Date: Fri, 8 Jul 2011 01:06:56 -0500 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Jamie Gritton <jamie@freebsd.org> Cc: freebsd-jail@freebsd.org Subject: Re: New jail(8) with configuration files, not yet in head Message-ID: <CALBk6yLF6fNw3VdR%2BoMymtMecQRgtZ2mQxwGG1iLZdb%2BYRYqFg@mail.gmail.com> In-Reply-To: <4E15475C.9020500@FreeBSD.org> References: <4E114EA9.4000605@FreeBSD.org> <CALBk6y%2BYWzOUzju-yN-bREX=4PY1pfhqX=QhW3K2qAExXkn8Mg@mail.gmail.com> <4E15475C.9020500@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 7, 2011 at 12:42 AM, Jamie Gritton <jamie@freebsd.org> wrote: > This is code that notes error return codes from processes run under the > jail (e.g. the exec.start script). But in this case, it's reporting an > error from a process that was part of the jail's shutdown. The reason > the command is "(null)" is this wasn't a command started from jail(8) > itself. > > I've fixed that dual-use bit of code to stay silent about existing > processes that die as part of jail shutdown. A small patch for that is > attached. > > - Jamie The patch silenced the errors and overall had a positive impact on jail shutdown time as well. It would be nice to hear more feedback from anyone involved in developing ezjail or qjail -- these ports will need reworking I assume. I'll try it myself and see, of course... -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALBk6yLF6fNw3VdR%2BoMymtMecQRgtZ2mQxwGG1iLZdb%2BYRYqFg>