Re: [opensuse] init.d script automatic start, not (just) run (solved)
On Mon, Apr 13, 2009 at 4:28 PM, ka1ifq <ka1ifq@sbcglobal.net> wrote:
On Monday 13 April 2009 17:19:07 you wrote:
On Thursday 09 April 2009 14:12:05 Neal Hogan wrote:
As you guys suspected, the network is not completely up when the script is called. I've tried the script both at runlevel 3 and 5 and various Required-Start options, including $network, $named, and $time.
My workaround (at this point) is to have a gnome session that starts the script. This requires that I open a terminal and execute the ssh connection there.
Thanks for your time.
Run it as the last startup script, maybe add a delay. Mike. -- I didn't want to not thank you for your suggestion . . . I thank you. I will be trying something soon and post what I've done for archival
On Fri, Apr 10, 2009 at 7:13 PM, ka1ifq <ka1ifq@sbcglobal.net> wrote: purposes.
As a matter of clarification, though, do you mean by "run as the last startup script" to name it in such a way that it runs last? The biggest problem I have is have the script run after the network is completely setup. I get errors involving dns resolution or that the network is unreachable.
-Neal Yes, run it as far after the network setup so the network is up and settled. Network is S05, so maybe an S99 if you don't already have one. I had to do this on another system for a similar reason.
According to my googling, S99 scripts are not a part of openSUSE (http://linux.derkeiler.com/Mailing-Lists/SuSE/2008-06/msg02663.html and other places). Anyway, I have taken you "delay advice" seriously and my init.d script points to a shell script that sleeps for 30 seconds and then runs the ssh command. Thanks for the help. -Neal
Good Luck.
-- www.nealhogan.net www.lambdaserver.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 14 Apr 2009 14:36:01 -0500, you wrote:
According to my googling, S99 scripts are not a part of openSUSE (http://linux.derkeiler.com/Mailing-Lists/SuSE/2008-06/msg02663.html and other places).
Yes, direct symlinks won't work long as the next installation of a package with init script(s) will cause insserv to recalculate dependencies and create syamlinks accordingly. The proper way is to use /etc/init.d/skeleton as the basis or template of your init script. Using $ALL in Required-Start will almost certainly be a good substitute for a S99 symlink. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Neal Hogan -
Philipp Thomas