🚀 go-pugleaf

In article <1993Jan7.213419.7488@ornl.gov> 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?

Yes 3.0 broke something.

The workaround is to call a shell script from rc.local, not to do anything  
directly in rc.local.

Haven't figured out why...
-- 
Michael Ross
Antigone Press, San Francisco, California
e-mail: mross@antigone.com
FAX: 1-415-431-3650

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

MMM.... personally, we call a bunch of things from rc.local under 3.0
with absolutely no problems:
(begin included /etc/rc.local)
#!/bin/sh -u
#
# This script is for augmenting the standard system startup commands. It is 
# executed automatically by the system during boot up. 
#
# Copyright (C) 1992 by NeXT Computer, Inc.  All rights reserved.
#
# As released orm, this script does nothing. You may customize
# it as you wish.
#

fbshow -A -B -E -I "Starting*Local*Services..."

# Read in configuration information
. /etc/hostconfig

# (echo -n 'local daemons:')					>/dev/console
#
# Run your own commands here
#
/usr/etc/accton /usr/adm/acct
# The above line initiates the accounting software startup.
# added: 11/2/92, 3:15 pm
# (echo '.')							>/dev/console

#
# The following line initiates the NetNews trn, thread database daemon
# mthreads.
/usr/local/lib/trn/mthreads -d60 -e
# added 11/12/92, 6:30pm, eoliver
# -d60 means run every 60 minutes.
# -e means do enhanced expiration check


/usr/etc/accton is a mach executable, as is mthreads, and mthreads run
with a '-d' is a daemon program which runs without any problems.

So, whatever your problem is, I somehow doubt it is a flaw in rc.local
itself.

-Erik