On Wed, 15 Dec 1999, Eugene wrote about, Re: Route daemon:
>
> Not exactly. I first attached my interfaces (eth &
> tr) and then I put 'routed' in rc.inet1. After
> booting up, I had to issue 'routed' again. That is
> all I was
> saying.
I dont know why it is, but i do have some thoughts as to why it wont start
properly if that really is the case.
You say you attach the 'tr' interface and start routed in rc.inet1, that is
one way of attaching an interface, but starting a daemon which writes to
the syslog before syslogd itself is started could be a reason why routed is
failing.
syslog is started from rc.inet2.
Network daemons are started after syslogd and klogd.
>
> > could possably be that
> > routed dies or just goes to sleep and does nothing
> > if interfaces are
> > attached after its started.
>
> It might well be, thanks!
>
> > On another note, you say in another mail you are
> > using .rhosts, you also
>
> My e-mails relating to $HOME/.rhosts and routed are
> independent of each other. I am talking about two
> different networks here.
>
> > say the network is a small one, now why would you
> > want to use routed
> > anyway, the .rhosts file + routed make your network
> > very "open" so you
>
> in a sense, yes!
>
> > Anyway routed should NOT be started from rc.inet1 it
> > should be called from
> > from rc.inet2.
>
> May I ask why? Aren't the two files: rc.inet1 &
> rc.inet2 - executed at boot time one after another?
yes.
> As I have read in some manual on Slackware networking,
> rc.inet2 serves as a complimentary file to rc.inet1
> (it finishes all network configurations that are not
> included in rc.inet1).
> Am I wrong?
It compliments them with the programs needed.
rc.inet1 attaches and configures network interfaces and adds routes for
those interfaces.
rc.inet2 starts daemons which run on those interfaces in the correct order.
So if program A relies on program B and program B gets started before
program A then it cant do its work properly so quite possably it will not
start or, start and then die, which is what you are seeing.
Its the same when loading kernel modules, they have dependancies, you have
to load them in the correct order otherwise problems will occour, or they
wont load at all.
>
>
> Thanks for the ideas!
>
> So long.
>
>
>
> =====
> <|>
> Eugene
> __________________________________________________
> Do You Yahoo!?
> Thousands of Stores. Millions of Products. All in one place.
> Yahoo! Shopping: http://shopping.yahoo.com
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
Merry Xmas.
