How do I empty the /tmp folder at boot?

Posty · 10-11-2003, 10:10 PM

Hello Slackware users.

How do I make Slackware empty the /tmp folder automatically each time I boot up?

Tarts · 10-11-2003, 11:02 PM

Make a script,

'vim /deltmp.sh' 'pico /deltmp.sh'

In this file put:

Code:

#!/bin/bash
rm /tmp/*

Add executable permission's to the file:

'chmod +x /deltmp.sh'

open '/etc/rc.d/rc.M'

add this line to the bottom:

Code:

if [ -x /deltmp.sh ]; then
  /deltmp.sh
else
  echo "'/deltmp.sh' does not exist." 
fi

But of course, there's alway's many way to do something.

Tarts

bender647 · 10-11-2003, 11:19 PM

If you look in /etc/rc.d/rc.S, there's a section
there commented "Clean up some temporary
files". You could just add /tmp to the end of
the list there.
___
Ken

[edit] /tmp/* of course

Posty · 10-12-2003, 03:04 PM

Adding /tmp/* to it didn't work.

The other way doesn't seem neccisary. I have had distros that empty it by default each boot.

Are there other things I may need to add? Like maybe cd /, blah blah something /tmp/*-/tmp?

As you can see I am confused, I am new to Linux (About three weeks new) and I would need this to be explained very plainly and clearly. Please help me out.

quatsch · 10-12-2003, 03:16 PM

I think you could add

rm -Rf /tmp
mkdir /tmp

at the very end of that file (/etc/rc.d/rc.S) or next to the section on cleaning up some temp files. This removes the tmp folder with all its contents and then creates an empty one.

synaptical · 10-12-2003, 03:19 PM

or just rm -Rf /tmp/*

edit: you could also put it in your shutdown scripts so it wouldn't slow down boot time. also IIRC it's a bit dangerous to delete tmp files after going into multiuser mode, so deleting at shutdown helps avoid that.

quatsch · 10-12-2003, 03:23 PM

Maybe I'm too stupid to figure this out but when I do
rm -Rf /tmp/*
it does not delete the hidden files... So I generally just remove the tmp folder and then recreate it (I do it manually from time to time; not at boot time)

Posty · 10-12-2003, 03:23 PM

Cool, I added that now. The thing is some of the text in there was black and some was white. I am useing Kwrite for this all. Anyways, I will reboot now and see if it works. Thanks for the quick reply.

synaptical · 10-12-2003, 03:29 PM

oh, you're right! the hidden files stay. sorry

for removing everything, your method is best.

Posty · 10-12-2003, 04:01 PM

Right, I will just remove the folder and recreate it then.

Also, and this is unrelated to the /tmp file, when I boot up a always get some "failed" stuff... Let me do dmesg...

i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected
i810_rng: RNG not detected

But when I am booting up it doesn't show it like that. But I know that those are what's causeing the problems. I always catch the "i810".. Any ideas on how to make these go away? So far I have not seen any problems with the functionality of my machine but seeing the errors and failed stuff makes me think there might be somehting wrong. Since these things are not starting and obviously are not needed because my PC is working just fine, can I stop these things?

taivu · 10-12-2003, 08:01 PM

Quote:

Originally posted by quatsch
Maybe I'm too stupid to figure this out but when I do
rm -Rf /tmp/*
it does not delete the hidden files... So I generally just remove the tmp folder and then recreate it (I do it manually from time to time; not at boot time)

rm -fR /tmp/* /tmp/.*

quatsch · 10-12-2003, 08:17 PM

Quote:

rm -fR /tmp/* /tmp/.*

right. except that
rm -Rf /tmp.*
complains that it cannot remove . or ..
which is of course a good thing but it still gives me the shivers. Imagine it succeeded in doing that - the whole file system up and down the whole structure deleted in one go.

bender647 · 10-12-2003, 08:26 PM

Hidden files would match /tmp/.* (rm -Rf /tmp/* /tmp/.*)

If you do choose to delete and remake /tmp, make sure
you reset the mode (permissions) properly. I believe its
chmod 1777 /tmp (drwxrwxrwt). You want the sticky bit
set so that even though anyone can write to /tmp, only the
owner of a file may remove the file. If you don't run
multi-user, you probably don't care, but its good practice
and probably good security.
___
Ken

smokybobo · 10-12-2003, 08:36 PM

If you want totally safe way with the bash shell you can use:

Code:

rm -rf /tmp/* /tmp/.[!.]*

or if you like regexp style:

Code:

rm -rf /tmp/* /tmp/.[^.]*

Of course, if there's a file with a name like '..four', then it doesn't really work, but then what really names a file/directory with two leading periods?