tmp files dumping 698
On Saturday 25 March 2006 04:15, CWO4 Dave Mann stood up and spoke the following words to the mbuttes incomp.os.linux.misc...:
The measure of cleaning out *-tmp* on boot is rather to be considered "useful" than as "the way to do it".
The best advice is to install something calledtmpwatch- other similar software exists - and to have *-tmp* and *-var-tmp* mounted with theatimeoption. This allows the system to keep track of the last time a file or directory was accessed.
tmpwatchcan then be set up to delete files from those two directories when they haven't been accessed for longer than - say - a day or two.
Furthermore, you could usecronto set up a script to do a similar thing on the files in your *-home-$USER-tmp* - but this too would require mounting *-home* withatimeenabled - or you could put a...
rm -rf ~-tmp-*
... in your *-home-$USER-.bashlogout. You could even add that to *-etc-skel-.bashlogout* so that it applies to every newly created user account.
On Fri, 24 Mar 2006 08:34:29 -0800, amanda It's Linux, BTW. ;-) The choice of a GNU-Linux distribution is a FAQ, and any recommendation tends to provoke...
*-usr-tmp* should be a symbolic link to *-var-tmp.* *-usr* is an otherwise static filesystem and should remain so. On my system, *-usr* is mounted read-only, even.
The symlink to *-var-tmp* then makes it possible to write to *-usr-tmp* for those archaic programs that still want to do that. ;-)
On Sun, 26 Mar 2006 08:11:14 -0800, amanda The initial releases of FC, that is 1 and 2, had problems, yes, but since 3, releases have been quite stable "right out of the box." And...
As long as you're running KDE or something similar, there will be files in *-tmp* that need access. Also bear in mind that for safety's sake, you should set *-tmp* and *-var-tmp* up with the sticky bit set.
On a normal UNIX workstation with one user account, about 100 MB of space for *-tmp* should be more than enough.
-- With kind regards,
*Aragorn* (Registered GNU-Linux user #223157)