On Wed, Dec 20, 2000 at 01:39:54PM -0800, Thomas Holton wrote:
>
> Thanks again:
>
> > > 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?
> no, makes up two lines
Right. It needs to be one line.
> > Are there any messages on /dev/console?
> no, there is nothing in /dev/console/
Once you make it one line you'll get them. You need to signal init
every time you change this file. Read the man pages on init and initab
to get an understanding of this mechanism.
> > What happens if you start up svscan manually?
> >
> > # cd /
> > # /usr/local/bin/svscan /service
> >
> > Show us the output.
> many messages:
> supervise: fatal: unable to start qmail-smtpd/run: access denied
> supervise: fatal: unable to start qmail-send/run: file does not exist
> supervise: fatal: unable to start log/run: access denied
You have a serious number of install errors. You should re-check every
step you made to ensure you followed the instructions exactly. The
errors you are getting occur when people don't follow instructions
to the letter.
And I do mean EXACTLY TO THE LETTER.
I suggest that for each step you do in the install, you then check
that what you've done is correct. If the instruct says to create a
file, do a cat to check it. If the instruction says to set a mode, use
an ls -l to check it. If you make a synmlink, make sure that it links
with ls -lL. Better yet, get a friend or peer to check each step with
you.
If the instructions aren't absolutely clear to you or your peer, ask
what they mean, don't guess. This list knows only too well that
guessers get it wrong - invariably.
Here's a simple example. What made you split the inittab entry into
two lines? Did you guess that it was ok?
Regards.
