home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!gatech!destroyer!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!atlantis!splunge!royce
- From: royce@splunge.uucp (Royce Howland)
- Subject: Re: rc.local?
- Message-ID: <1993Jan8.145805.18068@splunge.uucp>
- Organization: Ashley, Howland & Wood
- References: <1993Jan7.213419.7488@ornl.gov>
- Date: Fri, 8 Jan 1993 14:58:05 GMT
- Lines: 39
-
- woo@ornl.gov (John W. Wooten) writes:
-
- >I have a file rc.local in which I start my gopher daemon
- >and a supersrv daemon. Under 2.1 this worked fine. Now I find that
- >under 3.0, the script starts and prints out the
- >Starting local daemons:
- >and then the final .
-
- >In between are the parts to start the two daemons and they don't get
- >started!
- >If as su, I type sh /etc/rc.local (exactly what is in the rc script),
- >then the rc.local starts both daemons fine.
-
- >Any ideas on what I'm doing wrong?
- >- - - - - - - - -
-
- It's possible that your rc.local depends on some environment variables
- or other conditions being in place when it runs, and that such conditions
- are in place when you sh /etc/rc.local, and were in place under NS2.x,
- but are no longer in place under NS3.0. Think about things like the PATH
- and so on. Think about what else may be set when you're logged in as
- root (via su) that may not be set when the machine is booting.
-
- Put some diagnostic messages in rc.local, so you can at least see what's
- happening. If rc.local is doing things like
- if [ foo ]; then
- blah, blah, blah
- fi
- then modify this to be
- if [ foo ]; then
- blah, blah, blah
- else
- (echo Condition foo failed...) >/dev/console
- fi
- --
- Royce Howland, DKW Systems Corp. | "And since OS/2 2.0 is a 32-bit
- Everything is IMHO | operating system, programs are easier
- royce@splunge.uucp (NeXTMail OK) | to write and run faster, too."
- or kakwa!atlantis!splunge!royce | ad for OS/2 2.0
-