John Oliver wrote:
> We have a clunky old Red Hat 7.3 box here.  When it boots, it does not
> run /etc/rc.d/rc.local  This is a big problem because that's where I add
> static routes and start services that are dependant upon other hosts in
> other subnets! :-)
> 
> It's my understanding that rc.local is called by a symlink in the
> runlevel directory, and this is in place:
> 
> [EMAIL PROTECTED] root]# ls -l /etc/rc.d/rc3.d/S99local
> lrwxrwxrwx    1 root     root           11 Nov  9  2002
> /etc/rc.d/rc3.d/S99local -> ../rc.local
> [EMAIL PROTECTED] root]# ls -l /etc/rc.d/rc.local
> -rwxr-xr-x    1 root     root         1450 Dec 20 14:35
> /etc/rc.d/rc.local
> 
> [EMAIL PROTECTED] root]# cat /etc/rc.d/rc.local
> #!/bin/sh
> #
> # This script will be executed *after* all the other init scripts.
> # You can put your own initialization stuff in here if you don't
> # want to do the full Sys V style init stuff.
> 
> exit 0;
> 
> if [ -f /etc/redhat-release ]; then
>     R=$(cat /etc/redhat-release)
> 
>     arch=$(uname -m)
>     a="a"
>     case "_$arch" in
>             _a*) a="an";;
>             _i*) a="an";;
>     esac
> 
>     NUMPROC=`egrep -c "^cpu[0-9]+" /proc/stat`
>     if [ "$NUMPROC" -gt "1" ]; then
>         SMP="$NUMPROC-processor "
>         if [ "$NUMPROC" = "8" -o "$NUMPROC" = "11" ]; then
>             a="an"
>         else
>             a="a"
>         fi
>     fi
> 
>     # This will overwrite /etc/issue at every boot.  So, make any
> changes you
>     # want to make to /etc/issue here or you will lose them when you
> reboot.
>     echo "" > /etc/issue
>     echo "$R" >> /etc/issue
>     echo "Kernel $(uname -r) on $a $SMP$(uname -m)" >> /etc/issue
> 
>     cp -f /etc/issue /etc/issue.net
>     echo >> /etc/issue
> fi
> 
> /sbin/route add -net 192.168.2.0/24 gw 10.3.3.2
> #/etc/init.d/ypbind start
> /etc/init.d/ntpd start
> /etc/init.d/netfs start
> /etc/init.d/nfs start
> 
> touch /var/lock/subsys/local
> 
> 
> 
> /etc/issue and /var/lock/subsys/local aren't being touched, either.  I
> ran it manually, and there were no errors.
> 
> Any ideas?
> 

You maybe didn't notice the "exit 0" line at the top?

Regards,
..jim


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to