On Sat, May 18, 2002 at 05:32:23PM +0530, Philip S Tellis wrote:
> Sometime Today, H.S.Rai assembled some asciibets to say:
>
> > On finding solution to my problem by deleting content of /tmp,
> > I was thinking exactly what you suggested. BTW, is there any
> > drawback of cleaning up these directories at boot up or shut
> > down.
>
> yes. you'll have a hard time troubleshooting crashes and failures
> if you delete all the clues and evidence.
>
This is a matter of opinion. Many sysadmins and several distros
actually recommend this practice ... See the default setups of
debian, slackware and rock. Debian even clears /var/run & lock.
Besides, most stuff in /tmp are kept by users apps and are not
really of much use in a troubleshooting situation. In any case,
trobleshooting (if needed) is normally done while the system is
running and not after reboot. I have not faced this situation
of exploring /tmp for troubleshooting after reboot as yet ...
don't know if other have.
My personal view is, clearing /tmp at reboot should be the rec-
ommended practice. Yes, remove the dot files/ dirs as well.
Just my 2p.
Bish
--
:
####[ Linux One Stanza Tip (LOST) ]###########################
Sub : Starting X and keeping console free LOST #284
Make an alias or script for "startx &> .xsession-log &". This
creates a hidden file (.xsession-log) that you ca view later.
After running, you get your terminal back. Run vlock on this
terminal to lock it and prevent someone else from logging you
out or killing your X session while you're away.
####<Discussions on LIH: 31 Jan 2002>#########################
:
_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
