Xref: utzoo comp.misc:9894 comp.unix.questions:24909
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!ulysses!ulysses.att.com!andys
From: andys@ulysses.att.com (Andy Sherman)
Newsgroups: comp.misc,comp.unix.questions
Subject: Re: Your favourite rm in /tmp (was: Your favourite UNIX-pipe (...))
Summary: careful
Message-ID: <13633@ulysses.att.com>
Date: 22 Aug 90 12:58:55 GMT
References: <730@coma.UUCP> <2987@awdprime.UUCP> <2400@dino.cs.iastate.edu> <4002@rtifs1.UUCP> <58702@bbn.BBN.COM> <7249@star.cs.vu.nl>
Sender: netnews@ulysses.att.com
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 23

In article <7249@star.cs.vu.nl> maart@cs.vu.nl (Maarten Litmaath) writes:
>``On the other hand, adding '-r' makes some sense, unless you'd really like to
>leave a subdirectory of /tmp around forever.''  Sic!
>Also:
>	$ rm -r . ..
>	rm: cannot remove `.' or `..'
>	rm: cannot remove `.' or `..'
>
>Whatever:
>
>	$ rm .??* .[!.]		# not portable to every UNIX version

Umm, be careful.  We had a mysterious problem here with X11, where
after about 3 days new clients could not be started up to
DISPLAY=unix:0.0.  I finally figured out that our /tmp cleanup script,
which gets rid of trash which has not been accessed for 3 days, was
removing the UNIX(R) domain socket from /tmp/x11-unix.  :-(.
(Hint, only trash real files, and then remove empty directories.)

Andy Sherman/AT&T Bell Laboratories/Murray Hill, NJ
AUDIBLE:  (201) 582-5928
READABLE: andys@ulysses.att.com  or att!ulysses!andys
What? Me speak for AT&T?  You must be joking!