On Wed, Dec 20, 2000 at 12:50:05PM -0800, Thomas Holton wrote:
>
> Thanks for your prompt reply.
> The commands i put into the inittab file are the ones given in the
> documentation:
>
> SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin
> svscan /service </dev/null >/dev/console 2>/dev/console
All on one line?
SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service
</dev/null >/dev/console 2>/dev/console
Are there any messages on /dev/console?
What happens if you start up svscan manually?
# cd /
# /usr/local/bin/svscan /service
Show us the output.
Regards.
>
> since svscan is located /usr/local/bin, it is clearly in the path.
> Besides, the message is talking about respawning too fast... it is still
> doing it at this time as well. Any other information you can give is
> greatly appreciated!
>
>
> > On 20 Dec 2000, Mark Delany wrote:
> >
> > > On Wed, Dec 20, 2000 at 11:42:57AM -0800, Thomas Holton wrote:
> > > >
> > > > Hello, I installed svscan, as instructed for best performance with qmail,
> > >
> > > Well, svscan doesn't affect the performance of qmail - it affects the
> > > manageability and reliability of starting qmail.
> > >
> > > > and then i started qmail using csh because svscan did not start it in
> > > > enough time. now i have this message in my /var/log/messages file:
> > > >
> > > > Dec 2 .. init: Id "SV" respawning too fast: disabled for 5 minutes
> > > >
> > > > dont know how to fix this either, it has been doing this now for about 45
> > > > minutes... any ideas?
> > >
> > > This is actually a general Unix admin question, but be that as it
> > > may...
> > >
> > > You could have made make life a lot easier by showing us the inittab
> > > entry. Did you double-check that your inittab entry is correct? Did
> > > you read the inittab man page to understand what it's trying to do?
> > > How does that gel with the inittab entry you created?
> > >
> > > My guess is that you've got the path wrong to svscan or that the path
> > > points to something that isn't executable or that you've asked svscan
> > > to scan a directory that doesn't exist.
> > >
> > >
> > > Regards.
> > >
> >
>
