Subject: Re: [vserver] oom_adj error and sshd
From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
Date: Tue, 27 Jan 2009 14:51:38 -0500

On Wed, 2009-01-28 at 03:32 +0800, Jeffrey 'jf' Lim wrote:
> 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
Yes, the error is now only cosmetic - John
-- 
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan@opensourcedevel.com

http://www.spiritualoutreach.com
Making Christianity intelligible to secular society