Subject: Re: Is gcc slow? Or is our gcc slow?
To: None <current-users@NetBSD.ORG>
From: Rob Windsor <firstname.lastname@example.org>
Date: 04/11/1996 02:09:56
Verily did "Kevin P. Neal" write:
>>Personally, I (a) torch the clean-/tmp-on-reboot code in /etc/rc*, and
>>(b) make /usr/tmp and /var/tmp symlinks to /tmp. Oh, and (c) set up a
>>cronjob to clean out /tmp periodically.
> Hmmm, I'd be pretty upset if I was in the middle of something at some odd
> hour, like high noon or 4 in the morning, and /tmp went away.
I've seen this. The cronjob nukes files in /tmp that are over x hrs old
(what I saw had x defined to be 24). If you wanted to be creative, have
the cronjob nuke empty directories owned by users (those with a userid
> 1000 for example) afterwards.
If you want to tighten things up, just decrement x and decrease the time-
interval on the conjob.
I leave the 'clean-/tmp-on-reboot' code in since my /tmp is mfs anyway.
Internet: email@example.com Life: Rob@Sunnyvale.California.USA.Earth
"Da Web": http://pobox.com/~windsor/
"Ain't much distance 'tween a pat on the back and a kick in the pants."
-- David Lee Roth (1990), `The Dogtown Shuffle'