So being the idiot I can be sometimes here is what happened:

I just finally got my slackware64 installation multilib setup completed and was deciding lets now reinstall my graphics driver to get those 32bit libraries installed. So I install them and then I switch back to my normal user and find that my /tmp directory is pretty crowded and I can't stand this I examine it slightly and decide lets delete all this junk. I attempt this and fail to delete certain or any items so I switch back to root and do rm -r * the idiot I am for this I can't begin to describe. I have restarted my computer and now everything seems to work fine but is there anything I should worry about?

The /tmp directory is empty by default. There are several distribution which wipe /tmp anytime the system boots.

If you don't know about important data which you've stored on /tmp by yourself, there should be no problem.

There are although several applications which use /tmp for their temporary data (hence the name). Also the Slackpackages built from slackbuilds.org are stored in /tmp, so be careful if you use slackbuilds.org.

Markus

I'm glad to hear what you said until possibly up til slackbuilds...Isn't anything in /tmp safe for deleting (at least without issue) even if it's slackbuilds? if so then how could this get any worse :P I dont have much I have put on this system but it's how I installed alot of important stuff (like all but one thing that i've installed) :P but i do see no issues with anything installed from a slackbuild as far as i can tell but maybe I'm wrong and didn't install Java through a slackbuild cause I know java works fine I been using I do almost constantly but thanks for your reply

Don't get me wrong, the slackbuilds are built in this directory, once you have installed them you can delete the package. But I have a directory on my systems /usr/local/packages where I store the slackbuild-packages (I've several computers and use only one for package-building).

Markus

I see so long as I've installed the slackbuild I'm set then? That sounds better :P cause I checked if I installed Java through slackbuilds and turns out I did so and so I was like well there must be something i just don't understand thank you!

I wouldn't worry about it! I have modified the startup scripts on my home system to clear down anything in /tmp which is older than X days old.

Hello devnull10,

this is a good idea, you should provide the code and tell us how many days X is

Markus

Ten, if he's using Roman numerals.

1 members found this post helpful.

Yeah I'm not worried about it anymore I reinstalled the OS for other reasons but I also did find out prior to that, that everything works fine after I restarted the OS. Using slackware appartently at restart deletes and recreates files so that makes things simple . but if you would like please do post your code there for people to see incase there OS doesn't do this so they can clear out there tmp directory. or at least it can clear user files which don't get cleared. So we should say system temp files get deleted at restart.

Which then of course is written in Perl http://search.cpan.org/~dconway/Ling...a/Perligata.pm and http://search.cpan.org/~chorny/Roman/lib/Roman.pm

Markus

Yeah, mentioned here, too.

1 members found this post helpful.

Thanks for the link, I didn't know this thread, but sounds good

Markus

If anybody has any useful scripts, such as that mentioned by devnull10, please consider writing an article/HOWTO for the Slackware Documentation Project. Thanks.
http://docs.slackware.com/slackdocs:contributing