From: Corey Rogers <jrog@sunbeach.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Where to store routing informations
Date: Fri, 11 Apr 2003 09:23:17 +0000 [thread overview]
Message-ID: <marc-lartc-105005301213265@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105005242112765@msgid-missing>
Where ever you store your info always make sure it is documented. I
usually store mine in /etc/rc.d/init.d/routing (yes i create that
directory) and start it by creating a symlink in /etc/rc3.d/.
On occassion I store them in /root/bin.
Simply put you can store them anywhere you wish, just be consistent and
document where you placed them and how they are activated on boot.
On Fri, 2003-04-11 at 05:12, Keller Nicolas wrote:
> Hi,
>
> I just worked my way through the LARTC - thank you very much for this
> exellent piece of documentation :) However, I've got a newbie question:
>
> Where should I store routing informations? Are there prefered files in
> Redhat 9? /etc/sysconfig/static-routes has lost its function. I thought
> about making a bash script in /usr/local/sbin and call it at startup
> from /etc/rc.d/rc.local - is this a good or bad idea?
>
> I would be very glad, if someone could share its experiences with me.
> Perhaps that would also be a good point to be included in LARTC?
>
> Bye,
>
> Nicolas Keller
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
--
Corey Rogers <jrog@sunbeach.net>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-11 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 9:12 [LARTC] Where to store routing informations Keller Nicolas
2003-04-11 9:23 ` Corey Rogers [this message]
2003-04-11 14:01 ` christopher cuse
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=marc-lartc-105005301213265@msgid-missing \
--to=jrog@sunbeach.net \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.