Logic for network-scripts?

[Kevin Wang]

The default order of startup on FC with pcmcia devices is:

bring up pci ethernets
bring up network services
bring up pcmcia ethernets

that order obviously won't work if you want the network to be in place
before the network services come up.

So you should either chaneg the order of the services, or make the
pcmcia insertion restart the services you need.  I do this myself via
/sbin/ifup-local and /sbin/ifdown-local .  this script is run AFTER an
address is successfully gotten when an interface is brought up
(presuming dhcp).

My preference is the latter, because this way ANY interface that is
brought up will cause my network scripts to run.  this applies to both
wired and wireless.  All i need to do is run 'dhclient eth0' if at
boot time the wired ethernet was not connected, and the dhcp address
will be fetched, and the ifup scripts run afterwards.  (I think - I
have other scripts that run when dhcp succeeds, but that's a different
story).  it's been awhile since I looked at these things.  You should
have enough info to get started digging into the scripts and figure
out what each one does.

   - Kevin

On Mon, 16 Aug 2004 11:44:11 -0500, Harry Putnam <reader at newsguy.com> wrote:
> Joe Christy <joe at eshu.net> writes:
> 
> >   Vis-a-vis Harry Putnam's note of 08/16/2004 08:09 AM:
> >> ...
> >> Not really what you asked for... that is no test involved but would
> >> setting the ONBOOT parameter on one or the other to `NO' help?
> >> ...
> >
> >       Thanks, but you're right, that's not quite what I had in mind. If I'm
> > in the situation where the interface I need has ONBOOT unset, then when
> > I boot,  many subsequent network services, e.g. ntpdate, NFS mounts,
> > etc. fail and need to be started by hand, which is what I'd like to avoid.
> 
> First WARNING UNTESTED!!!
> 
> (I've done similar things but not this exactly so beware)
> 
> Set the ethernet device ONBOOT=NO
> 
> The scripts in /etc/rc.d/ have prefixes like S56blah which tell that
> script when to fire (inside a run level) The S means start and the
> number is a timing code.
> 
> Find the one that starts the wireless.  I'm guessing it might be:
> /etc/rc.d/rc3.d/10network
> 
> And insert your own script S17myscript  (I haven't researched
> exactly what the numbers mean so maybe something else here).  I think
> that would place it after syslog had started so any problems might at
> least get logged.
> 
> Your script could test for connectivity in an if/else thingy with a
> simple ping (ping -c1 <HOST>) possibly, to a known (normally up) host.
> 
> if it succedes your script runs ifup <device> else exit.
> 
> 
> 
> 
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>