For debugging purposes you might want to run svscan manually so the
errors go to the screen/window you're on.
On Fri, Feb 23, 2001 at 06:25:11PM -0500, Paul Farber wrote:
> Is there a specific kernel setting I need for supervise to log
Not unless it's some wierd Unix. svscan writes errors to stderr. You
don't need kernel settings to control where that goes.
> correctly??? I am on kernel 2.4.1.... it's working fine on a RH 6.2
> machine with 2.2.17 (using djbdns).
>
> The sticky bit seemed to have no effect..
Did you restart svscan?
> and nothing is being logged error-wise.
Did you check the system console?
Regards.
>
> Paul Farber
> Farber Technology
> [EMAIL PROTECTED]
> Ph 570-628-5303
> Fax 570-628-5545
>
> On Fri, 23 Feb 2001, Chris Johnson wrote:
>
> > On Fri, Feb 23, 2001 at 12:13:37PM -0500, Paul Farber wrote:
> > > drwxr-xr-x 4 root root 4096 Feb 21 01:40 service
> > >
> > > and under that
> > >
> > > drwxr-xr-x 4 root root 4096 Feb 21 01:40 .
> > > drwxr-xr-x 13 root qmail 4096 Feb 20 23:20 ..
> > > drwxr-sr-x 5 root root 4096 Feb 21 01:11 qmail
> > > drwxr-sr-x 5 root root 4096 Feb 21 01:35 qmail-smtpd
> > >
> > > Since the manual (man chmod) or the qmail-conf program docs didn't allude
> > > to it... what is the 'sticky bit'?
> >
> > chmod +t the directory. (Are you sure man chmod doesn't refer to this?)
> >
> > From http://cr.yp.to/daemontools/svscan.html:
> >
> > "If a subdirectory sub is sticky, svscan starts a pair of supervise processes,
> > one for sub, one for sub/log, with a pipe between them. svscan needs two free
> > descriptors for each pipe."
> >
> > Chris
> >
>
