[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3.2 Apache, newsyslog problem
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: 3.2 Apache, newsyslog problem
- From: Henning Brauer <lists-openbsd_(_at_)_bsws_(_dot_)_de>
- Date: Mon, 4 Nov 2002 23:45:35 +0100
- Mail-followup-to: misc_(_at_)_openbsd_(_dot_)_org
On Mon, Nov 04, 2002 at 04:52:40PM -0500, Peter Varga wrote:
> On Mon, Nov 04, 2002 at 10:36:24PM +0100, Henning Brauer wrote:
> > On Mon, Nov 04, 2002 at 08:16:20PM -0000, Stephen Marley wrote:
> > > However, the method of signalling httpd with
> > > SIGUSR1 used there doesn't work with a chrooted apache; instead it makes
> > > apache stop logging altogether.
> > uh? this should not happen.
> yes, it did happen to Oct 18 current. What fixed it was putting
> /dev/null under chroot directory. ( $chroot/dev/null ) While at it
> might as well have the zero too, and the random stuff.
> It is reproducable: loadmodule mod_perl, and Mason minimum config,
> then just the regular restart either SIGUSR1 or SIGHUP will do.
some 3rd party modules have have issues. this is no news.
we were talking about something else, read above.