From: Scott Taylor <scott@dctchambers.com>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: start up script
Date: Wed, 12 Feb 2003 07:33:46 -0800 [thread overview]
Message-ID: <5.1.1.6.0.20030212072135.00af1e68@mustang> (raw)
In-Reply-To: <200302120838.59057.unix@amigo.net.gt>
At 06:38 AM 2/12/03, - Luis - wrote:
>This is my script:
>
>#!/bin/bash
>/sbin/route add -net 10.3.1.0 netmask 255.255.255.0 gw 10.1.1.250
>/sbin/route add -net 10.4.1.0 netmask 255.255.255.0 gw 10.1.1.250
>/sbin/route add -net 10.8.1.0 netmask 255.255.255.0 gw 10.1.1.250
>
>and its place in /etc/rc.d/init.d/routetable and the link its in
>/etc/rc.d/rc3.d/S55routetable
There is more to writing a startup script than that.
>but i run it only executing /etc/rc.d/init.d/routetable as root
I don't think it should make a difference at this point, unless your
network isn't running by S55. Are you sure you are starting only at run
level 3?
>how does it work chkconfig? or do i have to place this script in somewhere
>else?
man chkconfig
It's a very handy tool for administering run level services.
Didn't you say you were running a RedHat box? Version number would be
useful information, however, check to see if you have the file:
/etc/sysconfig/static-routes
in it, add the line:
eth0 net 10.0.0.0 netmask 255.0.0.0 gw 10.1.1.250
>As long as eth0 is the NIC connected to 10.1.1.250
/etc/init.d/network script reads this file for you, and does it in the
right place, and the next person to admin this RedHat box will know where
to look with out a bunch of fumbling around.
Good luck.
Scott.
next prev parent reply other threads:[~2003-02-12 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 23:05 start up script - Luis -
2003-02-12 7:23 ` Glynn Clements
2003-02-12 8:35 ` freddie
2003-02-12 11:24 ` terry white
2003-02-12 14:38 ` - Luis -
2003-02-12 15:33 ` Scott Taylor [this message]
2003-02-12 17:45 ` - Luis -
2003-02-12 18:09 ` Jeff Largent
2003-02-12 18:29 ` - Luis -
2003-02-12 16:07 ` terry white
2003-02-12 22:14 ` Glynn Clements
2003-02-12 22:21 ` Andrew B. Cramer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.1.6.0.20030212072135.00af1e68@mustang \
--to=scott@dctchambers.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox