SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What is the purpose of /var/log/removed_packages and /var/log/removed_scripts. Can I remove them?
And one more thing - what tmp directories can be cleaned safely?
What is the purpose of /var/log/removed_packages and /var/log/removed_scripts. Can I remove them?
I don't know, but if I wanted to experiment, I would move them into another directory & see what happens.
Quote:
And one more thing - what tmp directories can be cleaned safely?
I currently run "rm -rf /tmp/*" in my rc.local.shutdown file. I used to do the same for /var/tmp, but read somewhere that that was not a good idea, so removed it, but I never had any problems with it.
Regards,
Bill
Here in the office we have a script that runs every evening to see what files in /tmp haven't been touched in the past month. If there are any such files, they are deleted.
Fairly easy to set up with cron and find, but a one-month rolling timeline has been my general ideology for some time.
Here in the office we have a script that runs every evening to see what files in /tmp haven't been touched in the past month. If there are any such files, they are deleted.
Fairly easy to set up with cron and find, but a one-month rolling timeline has been my general ideology for some time.
I don't know, but if I wanted to experiment, I would move them into another directory & see what happens.
I currently run "rm -rf /tmp/*" in my rc.local.shutdown file. I used to do the same for /var/tmp, but read somewhere that that was not a good idea, so removed it, but I never had any problems with it.
Someone misinformed you then. Nothing in /tmp or /var is supposed to be required to be preserved between boots. You could clear them both each and every time and everything runtime should still work. I just wouldn't make a habit of wiping out /var entirely (/var/tmp would be fine) because Slackware keeps it's package accounting data in there. Losing it won't break any daemons or anything, but it would effectively break the packaging tool for upgrades or package removals.
because Slackware keeps it's package accounting data in there. Losing it won't break any daemons or anything, but it would effectively break the packaging tool for upgrades or package removals.
Someone misinformed you then. Nothing in /tmp or /var is supposed to be required to be preserved between boots. You could clear them both each and every time and everything runtime should still work.
Thanks for the information. As I said above, I read that in a thread somewhere, & I guess one can read almost anything in a thread somewhere, right?
Regards,
Bill
/var/tmp is meant to hold info that should be preserved between boots. This doesn't mean that it should be required, though.
Most of /var is used for logs and lockfiles and shouldn't be completely wiped out -I mean you shouldn't remove the directories and the logfiles should exist, even if they are emptied(truncated) on shutdown.
/tmp can safely be cleaned out, except that there are a few invisible files there which it is convenient to preserve.
I did this before and it screwed up KDE. Since then I ran a script (I no longer run Slackware since Jan 2008) to see if the file had been modified in X days and then delete. That caused no problems.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.