On 09/14/2012 03:58 AM, Winnie Lacesso wrote:
Server has 16GB RAM 20GB swap; problem is, it's a compute server used by
many. So one user (later mortified remorseful, but) causes grief for
many. And a forced reset is always a concern re: possible filesystem
corruption.
Thank you all very much
On Sep 13, 2012, at 18:59 , Chris Schanzle wrote:
In our experience, if memory is allocated and never touched, it's like you
never allocated it at all (with respect to swap). Allocated but untouched
pages will not be swapped.
Right, but they do count as committed. Thus, once
Greetings,
Several times over past few years I've seen user processes go mad
(programming error) use all RAM, then all swap (as ganglia so vividly
shows), then the box ends up at a kernel panic.
(Server OS is SL5.x 64-bit BTW)
What's puzzling is, shouldn't the OS by default not allow users to
Hello Winnie,
On Sep 13, 2012, at 16:01 , Winnie Lacesso wrote:
Several times over past few years I've seen user processes go mad
(programming error) use all RAM, then all swap (as ganglia so vividly
shows), then the box ends up at a kernel panic.
(Server OS is SL5.x 64-bit BTW)
we
On 09/13/2012 10:32 AM, Stephan Wiesand wrote:
Hello Winnie,
On Sep 13, 2012, at 16:01 , Winnie Lacesso wrote:
Several times over past few years I've seen user processes go mad
(programming error) use all RAM, then all swap (as ganglia so vividly
shows), then the box ends up at a kernel
On Thu, Sep 13, 2012 at 04:32:00PM +0200, Stephan Wiesand wrote:
Hello Winnie,
On Sep 13, 2012, at 16:01 , Winnie Lacesso wrote:
Several times over past few years I've seen user processes go mad
(programming error) use all RAM, then all swap (as ganglia so vividly
shows), then the
