On Fri, 2010-05-07 at 17:25 +0200, Alexis Guéganno wrote:
On 7 May 2010 17:14, Hans Witvliet
wrote: On Mon, 2010-05-03 at 11:02 +0200, Stephan Kulow wrote:
Am Sonntag 02 Mai 2010 schrieb jdd:
I was just hit by this, please vote for
https://features.opensuse.org/307510
thanks :-)
We put tmpwatch in the default patterns, which takes care of this. Your variables only trigger on boot.
Greetings, Stephan
Other suggestion, Specially when /tmp is overpopulated, cleaning it the normal way can takes quite some time.
In case you don't mind cleaning it entirely (!), one might think about doing it the sun-os way: unmounting, reformatting, mouting: way faster!!
hw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi !
Doesn't it supposed that you mount /tmp on a dedicated partition ?
Cheers,
Agemen.
Well that's the best way to be sure any runaway program can not fill the entire disk, Just anything below that mount point.... When looking at systems that are intended to do some serious work work (in contrast to some play-configurations), you ooften see that /tmp, as well as /usr. /opt, /srv, /var, /var/log all got their own mount-points, (often using lvm, to allow growing, when size was not forseen properly) hw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org