Re: Autostarting NetworkManager in Fedora 8 prevents sshd to start properly

[Jim <jim howardweb org>]

I have the same sort of problem with Network Manager starting well after 
NFS...  go figure.

I imagine it has some other dependencies before it can start is the 
problem.  The startup order does need
to be looked into at some point however.

Jim



> > > Sounds like sshd is binding to an IP address and not handling changes
> > > when your IP address changes.  You should probably set up a
> > > NetworkManagerDispatcher script to kick sshd in the head (ie service
> > > sshd restart) when the network settings change.  This functionality
> > > should really be in sshd itself, doing something like avahi does where
> > > it watches netlink link & address events and handles the changes
> > > automatically.
> > >       
>
>   
> > I will try to change the start priority of avahi-daemon from 96 to 99
> > to see if it solves the problem.
> >     
>
> Changing the start priority of avahi-daemon didn't help. What about
> decreasing the start priority of the NetworkManager service from 98 to
> somewhat below the one of sshd? Is NetworkManager required to start so
> late (98)? Here are all current start positions of Fedora 8 in
> runlevel 5:
>
>