Date: Thu, 8 Feb 2007 18:12:35 +0000 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: /tmp getting full form portmanager Message-ID: <20070208181235.2cdd5de2@gumby.homeunix.com> In-Reply-To: <17867.18656.462978.486927@jerusalem.litteratus.org> References: <45CA6413.6000400@enabled.com> <20070207193234.BFA4.GERARD@seibercom.net> <45CA7215.7030004@enabled.com> <45CA9854.7040903@u.washington.edu> <45CAB605.1070901@enabled.com> <20070208145516.2a8612f8@gumby.homeunix.com> <17867.18656.462978.486927@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 8 Feb 2007 10:59:28 -0500 Robert Huff <roberthuff@rcn.com> wrote: > > RW writes: > > > > > clear_tmp_enable > > > > (bool) Set to ``YES'' to have /tmp cleaned at > > > > startup. > > > > And also daily_clean_tmps_enable (in periodic.conf) > > Before doing this, understand the consequences, > There's stuff in my /tmp ... I understand /who/ put it there, > but not /why/. Until I affirmatively know it's safe to delete, not > going to blindly reap the directory. It's not really doing it blindly, it only removes directories and ordinary files that haven't been accessed for three days (or whatever daily_clean_tmps_days is set to). There is also a list of things to ignore. It's safer than setting clear_tmp_enable with a /tmp linked to /var/tmp, since that's the proper place for temporary files that should survive a reboot.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070208181235.2cdd5de2>