home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.misc
- Path: sparky!uunet!cis.ohio-state.edu!udecc.engr.udayton.edu!blackbird.afit.af.mil!tschoole
- From: tschoole@afit.af.mil (Tony L. Schooler)
- Subject: Re: Why does OW leave all kind of garbage in tmp?
- Message-ID: <1992Jul29.123807.27681@afit.af.mil>
- Sender: news@afit.af.mil
- Nntp-Posting-Host: saturn.afit.af.mil
- Organization: Air Force Institute of Technology
- References: <1843@ltb.ltb.bso.nl> <1992Jul23.184344.15206@cbfsb.cb.att.com> <CKD.92Jul23233441@loiosh.eff.org> <1992Jul29.001208.1190@zia.aoc.nrao.edu>
- Date: Wed, 29 Jul 1992 12:38:07 GMT
- Lines: 30
-
- rmilner@zia.aoc.nrao.edu (Ruth Milner) writes:
-
- >In article <CKD.92Jul23233441@loiosh.eff.org> ckd@eff.org (Christopher Davis) writes:
- >>HEM> == hillel.e.markowitz <hillel@cbnewsf.cb.att.com>
- >>
- >> HEM> I would say that putting the following crontab (or similar) should
- >> HEM> be enough.
- >>
- >> HEM> 5 4 * * 6 rm -f /tmp/*
- >> HEM> Of course this assumes that nobody leaves anything important on /tmp.
- >>
- >>Like their /tmp/.X11-unix/* sockets for example?
- >>
- >>More than one person has found something breaking after a similar
- >>crontab was installed.
-
- >"rm -f /tmp/*" won't delete either files with names beginning with ".", or
- >subdirectories. So the OW stuff is safe from the above command on both counts.
-
- >Now, if you say "rm -rf /tmp/* /tmp/.[0-z]*", *then* you have problems ...
- >--
- >Ruth Milner NRAO/VLA Socorro NM
- >Computing Division Head rmilner@zia.aoc.nrao.edu
-
- We use "0 1 * * * (cd /tmp; find . -atime +1 -type f -exec rm -f {} \;)"
- in our crontab. That way, we do not remove a file that is in use.
-
- Anthony Schooler
- tschoole@afit.af.mil
-
-