David:
I am working through your method.
I did write /etc/init.d/localvipa using the sample from zebra. I modified
/etc/init.d/zebra to require localvipa.
The /etc/init.d/localvipa is calling a perl program in
/usr/local/sbin/localvipa.pl that I wrote. It passes one of three
parameters "start/stop/status".
It checks the presense of dummy0, eth0 and eth1. If one of them is
missing, then issues a warning.
It tests fine.
I'd like to thank you and thank Rick Troth for giving me a hand. I am sure
by the time I revisit this approach and re-write version II, it will be
fancier.
Right now I got some deadlines on the implementation of zLinux so I better
move on to my other challenges.
Regards,
[EMAIL PROTECTED]
NCCI
Boca Raton, Florida
561.893.2415
greetings / avec mes meilleures salutations / Cordialmente
mit freundlichen Gr��en / Med v�nlig h�lsning
David Boyes
<[EMAIL PROTECTED] To:
[email protected]
e.net> cc:
Sent by: Linux on Subject: Re: init script
390 Port
<[EMAIL PROTECTED]
IST.EDU>
06/06/2005 04:29
PM
Please respond to
Linux on 390 Port
> I am trying to figure out a simple approach for executing the
> following two
> commands before the zebra and ospfd deamons come up (rc 2/3/5).
You need to do two things:
1) Create a init script that executes the qeth commands you want.
2) Modify the zebra startup script to require the queth script to run
first.
To do #1:
Take one of the existing startup scripts and look at the comment block
at the top (i used the one for named from SuSE 8.x here as an example):
#! /bin/sh
# Copyright (c) 1995-2001 SuSE GmbH Nuernberg, Germany
#
# init.d/named
#
### BEGIN INIT INFO
# Provides: named
# Required-Start: $network $remote_fs $syslog
# Required-Stop:
# Default-Start: 3 5
# Default-Stop:
# Description: Starts internet domain name server (DNS)
### END INIT INFO
Edit the Provides: line to provide a string like "qeth-setup-commands".
Modify the "start)" section of your script to execute your qeth commands
and optionally, the "stop" section to undo the commands (neatness counts
here). Your script should source /etc/sysconfig/qeth-setup-commands by
doing:
. /etc/sysconfig/qeth-setup-commands
early on in the script as the source for the IP addresses, to allow you
to easily change them on all your systems.
Use insserv to install your init script and chkconfig to turn your
script on in the appropriate runlevels if need be.
To do #2:
Modify the zebra init script by adding "$qeth-setup-commands" to the
Required-Start: line in the init info comments.
Run "chkconfig zebra off;chkconfig zebra on" to force SuSE to rebuild
the init dependencies and resequence the links in /etc/rc.n for each
runlevel.
That will prevent the SuSE tools from screwing up your boot process, and
if you add new software, all the links are properly maintained.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work product and
as such is privileged and confidential. If the reader of this message
is not the intended recipient or an agent responsible for delivering it
to the intended recipient, you are hereby notified that you have
received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you
have received this communication in error, please notify us immediately
by e-mail, and delete the original message.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
