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.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
/tmp filling up
I did my usual df -h and I saw that my system had grown 1.2 G from its former happy size over the past week. WTF!?
I cruised around until I found 1.2G worth of stuff on /tmp.
I was in a good mood, so I blasted all of it. Luckily, the system still comes up fine.
How are you guys managing /tmp? I have logrotate working fine (FYI for new guys, you have to force it once to set the dates or it won't ever work) and so that part is under control.
the /tmp contents on my PC get cleared upon proper reboot/shutdown - i added a couple lines to /etc/rc.d/rc.0 in order for that to happen... of course on a server this wouldn't be the right approach...
If you use tmpfs for /tmp then it automatically is cleared on reboot. Is there a reason you don't have it setup like that?
i can't speak for randux, but the reason i don't use shmfs/tmpfs on my box's /tmp is cuz i do a lot of stuff in /tmp and i really don't want that stuff to impact my RAM...
Yeah, though I'm not sure if you had a structure like
/tmp
/tmp/foo
/tmp/foo/bar.txt
and bar.txt was accessed or edited if /tmp and /tmp/foo would be marked as accessed, so I also do a check for if a file is a directory
Code:
find /tmp -regex '^/tmp/.*' -atime +6 | sort -r \
| while read file; do
if [ -d "$file" ]; then
rmdir --ignore-fail-on-non-empty "$file"
else
rm -f "$file"
fi
done
The regex means that the dir /tmp will never be deleted, otherwise if it hasn't been accessed for 7 days and it was empty it would be deleted. Of course that would fail if the search path '/tmp' had a trailing slash. Also 6 instead of 7 because find ignores fractional days.
For reference, on the workstation in rc.shutdown (arch) I have
question about your rc.0/rc.shutdown line: why no sticky bit?? just curious...
I think that may be a side affect of trying to do an install at 3 in the morning and keep saying to myself: "If I can just get to point X, then I'll be happy and go to bed". I've never picked up on it since. However I've changed it now, thanks for pointing it out.
Quote:
Originally Posted by win32sux
question #2: my server's filesystems (reiserfs v3) get mounted with the "noatime" option... does that make the find by atime not doable??
From what I understand no, two solutions spring to mind though. Either use the last modified property (mtime I think), or better IMHO (which is what I do) have /tmp on a separate partition and don't use noatime for that partition
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.