I think that I am having problems with my /etc/rc.d/rc.local. I have put adsl-start in the script. It did work until Monday when I updated my box to the new packages for current. I inadvertently replaced a few conf by nothing affecting the network configuration, or so I thought. Upon a reboot the adsl connection did not come up automatically. But if I run /etc/rc.d/rc.local start after boot it comes up fine. I tried changing the permissions by chmod +x /etc/rc.d/rc.local. What should the file permissions be set at to bring up the script at start up? I boot into run level 4. Thanks.

I don't think it is permission problem, I would try
add a delay before execute the command like :

(sleep 5 && adsl-start) &

Make sure the rc.local script is being excecuted or called upon by your rc.M script.. preferrably at the end of the script..

well, I changed the rc.local around similar to what keefaz suggested:

#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local setup commands in here:

sleep 5 && adsl-start &


trickykid,

I check the rc.M file and it appears to be calling ti up at the end:

#!/bin/sh
#
***Removed Big Chunk***

# Start the local setup procedure.
if [ -x /etc/rc.d/rc.local ]; then
. /etc/rc.d/rc.local
fi

# All done.


I got the same result. Any clues?

Maybe some terminal output congestion ?
I don't know/never used this script but did you tried to call it with suppressed output like this
?

adsl-start works fine. it's the rc.local that is not working correctly.

well...( really, no offence but... ) he asked you to check it, you don't have to post such files.
( we all got the same one i guess... )

egag

egag,

you never what can help. That is what we are all here for.

So is rc.local even executable?

chmod +x rc.local

And have you tried putting the full path to your adsl-start script/command?

If you can run it after you boot and it works, perhaps you should put an echo line in there to test if its being executed or not.

Add something like this to your rc.local file:

And you can test it by running..

Which will print out what its doing from the script, etc. But you should really be using a script like this I found from googling.. http://www.hupo.org.cn/docs/linuxdoc...3.5/adsl-start

Then you can specify it from rc.M and have it separate from your rc.local file.

rc.local is definitely exectuable. I am just not sure why it is not running on boot. My adsl-start file look just like the one in the link. I am going to reboot with those options you stated for the rc.local. My report will follow.

Aftering adding the lines:

echo "Starting ADSL Services... "

CONFIG=/etc/ppp/pppoe.conf

/usr/sbin/adsl-status $CONFIG > /dev/null 2>&1

to the rc.local I am able to see the "Starting ADSL Services...." prior to the start of X. But I got the same result. I run rc.local manually, no problem.

Usualy there is the only difference between running rc.local from multiuser startup script rc.M and from interactive shell in shell startup scripts so looking into them may help (depends on used shell: /etc/profile, ~/.profile, ~/.bash_profile, ~/.bash_login, ~/.cshrc, ~/.login, ...). Maybe some environment setting is required ?

yes ok...i didn't mean anything wrong...
just pain in my finger from scrolling...

but the sripts all are executed, so i think you'll need to give it a small time out
as keefaz wrote
like:

--------------
sleep 5
echo "Starting ADSL Services... "

CONFIG=/etc/ppp/pppoe.conf

/usr/sbin/adsl-status $CONFIG > /dev/null 2>&1
--------------

( or do you have that allready ? )

egag

I will try adding that.

I changed my rc.local to this:

#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local setup commands in here:

echo "Starting ADSL Services... "

adsl-start

echo "..Connected"


But during boot it timed out and then displayed the connected part. When is ran the script for the CLI it worked perfectly. Weird. I am kinda at a loss.

no news on the " sleep 5 " addition ?

egag