Am Mon, 21 Dec 2015 23:20:24 +0000
schrieb Mick <michaelkintz...@gmail.com>:

> On Monday 21 Dec 2015 22:38:21 Alan McKinnon wrote:
> > On 22/12/2015 00:37, Mick wrote:
> 
> > > Am I alone in experiencing this?  Any ideas for fixing it?
> > > Should I post a bug and if so where?  I'm thinking that asking
> > > Lennart to fix ifplugd so that it works with openrc would be
> > > taking it a step too far.  :p
> > 
> > read the news items for the last 3 months or so.
> > 
> > openrc changes, networking and service dependencies have changed
> > somewhat, all well documented in the news items
> 
> Thank you Alan, I believe I've read the news item you refer to, but I
> am not sure I understand how or why it applies to two laptops.  The
> news item refers to localmount and netmount which if they cannot be
> mounted will cause problems.  I don't use netmount on these laptops:
> 
> # rc-update -s -v | grep mount
>            localmount | boot                                          
>              mount-ro |                        shutdown               
>              netmount |
> 
> 
> localmount works and I see no failures in mounting my filesystems.
> What fails repeatably is ifplugd, which no longer starts wired or
> wireless devices.
> 

You could try running the service in debug mode (--debug), and look at
the line starting ifplugd. Check if the parameters look correct, then
try to fire the same command from command line and check the console
output for errors.

By the way: Is ifplugd still needed? I thought it has been replacable
by openrcs improved hotplug/coldplug support a long time ago? I
remember my main purpose of using ifplugd back the days I still used it
was to decouple the network init latency from the rest of the boot
process and thus speed it up - in addition to the benefit of not
starting some services at all when no network was plugged in.

Part of the problem may be that udev handles device renaming and
bootstrapping now. Maybe ifplugd should be called from udev and no
longer be a service? In the end, ifplugd is tied to the device name -
and thus must be part of the device service it is going to manage. And
I don't think this is how it works in openrc nowadays. Thus it needs
to move deeper down the layer - which is udev.

Alternatively, NetworkManager is probably also a good replacement then -
tho I totally understand why you wouldn't want to install it. At least
you wouldn't have to ask Lennart then for fixing ifplugd in openrc
if problems arise. ;-)

As a side note: systemd-networkd handles and fits the same purpose as
ifplugd very well - should you consider to migrate to systemd. *scnr*

It's also not by Lennart, which elevates your problems with asking
Lennart to fix something. :-)

-- 
Regards,
Kai

Replies to list-only preferred.

Attachment: signature.asc
Description: PGP signature

Reply via email to