Marcy:
I tried but boot.local gets executed before QDIO is up so they failed.
The other problem is that the IP address will change depending on factors
outside our control.
I wrote a short program, vipa.pl that I put in /etc/init.d. I am about to
go to yast to activate it.
I also changed zebra so it requires "vipa" before it starts its runlevel.
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
Marcy Cortes
<[EMAIL PROTECTED] To:
[email protected]
sfargo.com> cc:
Sent by: Linux on Subject: Re: init script
390 Port
<[EMAIL PROTECTED]
.EDU>
06/06/2005 04:06 PM
Please respond to
Linux on 390 Port
If you are running SuSE, I think you could try them in
/etc/init.d/boot.local (issue chkconfig and make sure boot.local is "on").
Marcy Cortes
This message may contain confidential and/or privileged information. If
you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any action based on this message or
any information herein. If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message.
Thank you for your cooperation."
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Uriel
Carrasquilla
Sent: Monday, June 06, 2005 12:54
To: [email protected]
Subject: [LINUX-390] init script
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).
1) qethconf vipa add 172.27.108.10 eth0
2) qethconf vipa add 172.27.108.10 eth1
Both zebra and ospfd are in the /etc/init.d. They both have proper
Required-start and they come up OK.
The problem is that zebra needs to have the qethconf issued before zebra
comes up.
I thought of putting the two commands inside /etc/init.d/zebra but
unfortunately the IP address can change in situations on which we backup
the system and bring it up as a different server with a new IP address (or
in DR).
The other approach I thought would be to write my own script that can be
executed from /etc/init.d. This will be a new thing for me to do.
I was hoping I can get some advise from this group for new ideas.
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
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
----------------------------------------------------------------------
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
