View Single Post
Old 02-14-2012, 05:04 AM   #4
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by cscat View Post
Alert BEFORE reboot if space in /var is limited:
- - snip - -
I'll implement this in future.
That is something which "should never happen" (famous last words) on Linux or any *nix system.

The system should "boot" under any conditions because the file systems used in *nix reserve a percentage of the storage area for the use of root.
Then the initialization process (init, pid 1) runs as user "root".

Just because init will run and boot the system, that does not mean that some of the userland programs which it starts will not run out of room.

It might be of more use to find out why the system behaves the way you describe and fix the cause.
One of the first things to check would be what value has been set for the root file system reserved area. It is possible that it is set too small or has been even reduced to nothing.
knc1 is offline   Reply With Quote