Subject: Re: [vserver] oom_adj error and sshd
From: "Jeffrey 'jf' Lim" <jfs.world@gmail.com>
Date: Wed, 28 Jan 2009 03:32:45 +0800

On Wed, Jan 28, 2009 at 2:29 AM, Herbert Poetzl <herbert@13thfloor.at> wrote:
> On Thu, Jan 22, 2009 at 11:48:32AM -0500, John A. Sullivan III wrote:
>
>> I also gather the guest is really not controlling memory but I
>> assume writing this to proc would tell the host to not kill this
>> sshd process on the guest. Is that correct? Thanks - John
>
> yes, and the correct handling in the script would be to check
> if that entry is available and writeable, and if not, then it
> should silently ignore the fact, instead of bailing out
>

perhaps file a bug report upstream? Right now, the script only checks
if the entry is availabe ('if [ -e "/proc/$PID/oom_adj" ]'). The
script used to bail out (or rather, it gave a problem with upgrading)
- but I think the problem has been fixed now (there was a bug report
filed previously in debian about this).

-jf