Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site soessx.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!akguc!soessx!pls
From: pls@soessx.UUCP (P.L.Sullivan)
Newsgroups: net.unix-wizards
Subject: Re: Another reason why - really /tmp
Message-ID: <717@soessx.UUCP>
Date: Sat, 28-Sep-85 00:16:16 EDT
Article-I.D.: soessx.717
Posted: Sat Sep 28 00:16:16 1985
Date-Received: Sun, 29-Sep-85 06:33:41 EDT
References: <1149@brl-tgr.ARPA> <182@graffiti.UUCP> <764@rlgvax.UUCP> <2279@sunybcs.UUCP>
Reply-To: pls@soessx.UUCP (P.L.Sullivan)
Organization: AT&T Tech-NS, Atlanta
Lines: 18
Keywords: mkfs

In article <2279@sunybcs.UUCP> loverso@sunybcs.UUCP (John Robert LoVerso) writes:
>From: peter@rlgvax.UUCP (Peter Klosky) 16 Sep 85 <764@rlgvax.UUCP>
>> > For security make your /tmp file 0600 mode.
>
>I also changed /etc/rc to clear /tmp with an rm -r
>

If you have the luxury of a separate /tmp file system it is even more 
efficient and often takes less time than "rm -r" to simply do a "mkfs" 
over the old one.  The big advantage is that the free list gets 
reassembled for optimum access rather than being frag'ed all over 
the file system.

(I know - If you don't, "fsck -s..." does just about as much good (:-).

==================================================================
Pat Sullivan - {akgua|akguc|ihnp4}!soessx!pls - voice 404-257-7382


Brought to you by Super Global Mega Corp .com