Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Mick]

On Tuesday 22 Dec 2015 23:32:40 Neil Bothwick wrote:
> On Tue, 22 Dec 2015 15:15:57 +, Mick wrote:
> > > As far as I understood, you now start ifplugd using the associated
> > > net.* init script. Openrc will detect that ifplugd is installed and
> > > then wait until a cable is plugged, plus starting an instance
> > > listening on the device.
> > 
> > No, this is not how ifplugd worked, for as long as I can remember.  I
> > never started the interface, or had to start ifplugd by an init.d
> > script or manually.
> 
> It may not be how you used it, but that is how ifplugd (or netplug) is
> supposed to be used with openrc. It detects whether ifplugd or netplug is
> installed when the interface is started up and starts it up to monitor
> the interface using the correct options. It's been that way fr a lot of
> years and was documented, I think in the comments in the net.* scripts.
> 
> Your approach may have worked in the past but it was unsupported, now it
> appears that it doesn't work.

Thank you Neil, I just tried netplug and indeed behaves the same as ifplugd - 
one has to start the interface before netplug will configure a connection.

Interestingly, there is a difference between netplug and ifplugd.  ifplugd 
when started by hand, will initialise and configure a NIC.  netplug will not.  
It requires that the interface has been enabled before it does anything.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Mick]

On Tuesday 22 Dec 2015 14:20:26 Kai Krakow wrote:
> Am Tue, 22 Dec 2015 14:04:12 +
> 
> schrieb Mick :

> > There is no means of enabling or disabling the ifplugd service that I
> > have found, because there is no /etc/init.d/ifplugd script.  Once
> > installed ifplugd always starts at boot and daemonizes, configuring
> > or tearing down connections as a link is detected or lost.
> 
> As far as I understood, you now start ifplugd using the associated
> net.* init script. Openrc will detect that ifplugd is installed and
> then wait until a cable is plugged, plus starting an instance listening
> on the device.

No, this is not how ifplugd worked, for as long as I can remember.  I never 
started the interface, or had to start ifplugd by an init.d script or 
manually.


> Its clear how it used to work but I think the semantics changed. Since
> I do no longer use openrc I cannot confirm how the rest of the services
> react to and activated net.* init script if ifplugd is active through
> the plugin. I suppose dependent scripts should only be triggered after
> the cable is plugged in.
> 
> This is also why there is no config file: Its configured dynamically
> through the plugin and the interface specific init script.

I can confirm that the config file is only used by the /etc/init.d/ifplugd 
script - which however does not exist on Gentoo.

I created a config file, specified the enp11s0 there, started 
/usr/sbin/ifplugd manually and it still tried to bring up the default eth0 
interface.

Starting ifplugd manually with '-i enp11s0' works as intended.  It brings up 
the NIC and configures the interface:

 ifplugd(enp11s0)[4275]: ifplugd 0.28 initializing.
 ifplugd(enp11s0)[4275]: Using interface enp11s0/00:26:B9:20:B4:9C with driver 
 (version: 3.137)
 ifplugd(enp11s0)[4275]: Using detection mode: SIOCETHTOOL
 ifplugd(enp11s0)[4275]: Initialization complete, link beat not detected.
 kernel: IPv6: ADDRCONF(NETDEV_UP): enp11s0: link is not ready
 kernel: tg3 :0b:00.0 enp11s0: Link is up at 100 Mbps, full duplex
 kernel: tg3 :0b:00.0 enp11s0: Flow control is on for TX and on for RX
 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp11s0: link becomes ready
 ifplugd(enp11s0)[4275]: Link beat detected.
 ifplugd(enp11s0)[4275]: Executing '/etc/ifplugd/ifplugd.action enp11s0 up'.


> > I started this thread because recently I have to start my wired
> > interface manually, after which point ipfplugd also starts,
> > daemonizes and manages the connection.  This is not how it used to
> > work - I never had to start the wired interface myself.
> 
> This is how it works now: ifplugd is started through the interface
> script.

I hear what you say.  However, this makes me ask - what changed to cause this?  
Things changed since dev-libs/libgudev-230 and sys-fs/udev-225 were installed.  
<=sys-fs/udev-216 and friends used to bring up ifplugd(enp11s0) without any 
intervention from me or from /etc/init.d/ scripts.  So I have to guess that 
something changed in udev to cause this change in behaviour.

Thank you for helping me walk through this.  I'm going to raise a bug report 
and see what the devs think.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Neil Bothwick]

On Tue, 22 Dec 2015 15:15:57 +, Mick wrote:

> > As far as I understood, you now start ifplugd using the associated
> > net.* init script. Openrc will detect that ifplugd is installed and
> > then wait until a cable is plugged, plus starting an instance
> > listening on the device.  
> 
> No, this is not how ifplugd worked, for as long as I can remember.  I
> never started the interface, or had to start ifplugd by an init.d
> script or manually.

It may not be how you used it, but that is how ifplugd (or netplug) is
supposed to be used with openrc. It detects whether ifplugd or netplug is
installed when the interface is started up and starts it up to monitor
the interface using the correct options. It's been that way fr a lot of
years and was documented, I think in the comments in the net.* scripts.

Your approach may have worked in the past but it was unsupported, now it
appears that it doesn't work.


-- 
Neil Bothwick

WYTYSYDG - What you thought you saw, you didn't get.


pgpqLHMOQkCzt.pgp
Description: OpenPGP digital signature

[gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Kai Krakow]

Am Tue, 22 Dec 2015 14:04:12 +
schrieb Mick :

> On Tuesday 22 Dec 2015 01:12:10 Kai Krakow wrote:
> > Am Tue, 22 Dec 2015 00:54:35 +
> > 
> > schrieb Mick :
> > > On Tuesday 22 Dec 2015 00:48:13 Neil Bothwick wrote:
> > > > On Mon, 21 Dec 2015 23:55:06 +, Mick wrote:
> > > > > > Are you trying to run ifplugd from its init script? It's not
> > > > > > meant to be used like that with openrc.
> > > > > 
> > > > > I don't have any init scripts for ifplugd.  I wondered what
> > > > > starts it/stops it, and found /lib64/netifrc/net/ifplugd.sh
> > > > 
> > > > It should be started by the net.eth* scripts, so you need to
> > > > start the network interface first.
> > > 
> > > Thanks again Neil.  I don't think this is as you suggest.  I never
> > > had wired or wireless interfaces enabled to start at boot time,
> > > because ifplugd started them up as necessary.
> > > 
> > > From the README file:
> > >The network interface which is controlled by ifplugd should
> > > not be configured automatically by your distribution's network
> > > subsystem, since ifplugd will do this for you if needed.
> > 
> > But that doesn't apply here because the "net.* plugin" starts
> > ifplugd, and defers further initializations until ifplugd detects a
> > link.
> > 
> > This is what I meant when I talked about pushing ifplugd further
> > down the layer. I just didn't remember that this is now solved by a
> > plugin in net.* itself.
> > 
> > Don't enable ifplugd service. Openrc will do its magic.
> 
> There is no means of enabling or disabling the ifplugd service that I
> have found, because there is no /etc/init.d/ifplugd script.  Once
> installed ifplugd always starts at boot and daemonizes, configuring
> or tearing down connections as a link is detected or lost.

As far as I understood, you now start ifplugd using the associated
net.* init script. Openrc will detect that ifplugd is installed and
then wait until a cable is plugged, plus starting an instance listening
on the device.

> To make it clearer, this is how it used to work on two laptops:
> 
> I install ifplugd and remove from rc-update any net. that I
> have configured.  ifplugd will always start at boot as a daemon and
> will bring up and configure the wired NIC once a cable is detected.
> There is no start up script in /etc/init.d/ installed by default,
> although the man page mentions it, along
> with /etc/ifplugd/ifplugd.conf, which is also not installed.  This is
> the only file that installed on my systems:
> 
> # find /etc -iname *ifplug*
> /etc/ifplugd
> /etc/ifplugd/ifplugd.action

Its clear how it used to work but I think the semantics changed. Since
I do no longer use openrc I cannot confirm how the rest of the services
react to and activated net.* init script if ifplugd is active through
the plugin. I suppose dependent scripts should only be triggered after
the cable is plugged in.

This is also why there is no config file: Its configured dynamically
through the plugin and the interface specific init script.

> I started this thread because recently I have to start my wired
> interface manually, after which point ipfplugd also starts,
> daemonizes and manages the connection.  This is not how it used to
> work - I never had to start the wired interface myself.

This is how it works now: ifplugd is started through the interface
script.

You may need to start and stop network dependent service through
ifplugd.action instead of enabling them statically through openrc. But
again: I'm not sure about it. It may be worth a try.

> Furthermore, starting ifplugd on a terminal now shows that it is
> listening on eth0 instead of enp11s0, but hadn't tried this before
> things broke.  According to the man page eth0 is the default, but I
> can't recall manually specifying a different interface for ifplugd in
> the past.  It always brought up the wired interface, no matter what
> it was called.

This is due to its defaults mentioned in the man page: It defaults to
eth0. Gentoo no longer installs a config file.


-- 
Regards,
Kai

Replies to list-only preferred.


signature.asc
Description: PGP signature

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Mick]

On Tuesday 22 Dec 2015 01:12:10 Kai Krakow wrote:
> Am Tue, 22 Dec 2015 00:54:35 +
> 
> schrieb Mick :
> > On Tuesday 22 Dec 2015 00:48:13 Neil Bothwick wrote:
> > > On Mon, 21 Dec 2015 23:55:06 +, Mick wrote:
> > > > > Are you trying to run ifplugd from its init script? It's not
> > > > > meant to be used like that with openrc.
> > > > 
> > > > I don't have any init scripts for ifplugd.  I wondered what starts
> > > > it/stops it, and found /lib64/netifrc/net/ifplugd.sh
> > > 
> > > It should be started by the net.eth* scripts, so you need to start
> > > the network interface first.
> > 
> > Thanks again Neil.  I don't think this is as you suggest.  I never
> > had wired or wireless interfaces enabled to start at boot time,
> > because ifplugd started them up as necessary.
> > 
> > From the README file:
> >The network interface which is controlled by ifplugd should not be
> >configured automatically by your distribution's network subsystem,
> >since ifplugd will do this for you if needed.
> 
> But that doesn't apply here because the "net.* plugin" starts ifplugd,
> and defers further initializations until ifplugd detects a link.
> 
> This is what I meant when I talked about pushing ifplugd further down
> the layer. I just didn't remember that this is now solved by a plugin
> in net.* itself.
> 
> Don't enable ifplugd service. Openrc will do its magic.

There is no means of enabling or disabling the ifplugd service that I have 
found, because there is no /etc/init.d/ifplugd script.  Once installed ifplugd 
always starts at boot and daemonizes, configuring or tearing down connections 
as a link is detected or lost.

To make it clearer, this is how it used to work on two laptops:

I install ifplugd and remove from rc-update any net. that I have 
configured.  ifplugd will always start at boot as a daemon and will bring up 
and configure the wired NIC once a cable is detected.  There is no start up 
script in /etc/init.d/ installed by default, although the man page mentions 
it, along with /etc/ifplugd/ifplugd.conf, which is also not installed.  This 
is the only file that installed on my systems:

# find /etc -iname *ifplug*
/etc/ifplugd
/etc/ifplugd/ifplugd.action


I started this thread because recently I have to start my wired interface 
manually, after which point ipfplugd also starts, daemonizes and manages the 
connection.  This is not how it used to work - I never had to start the wired 
interface myself.

Furthermore, starting ifplugd on a terminal now shows that it is listening on 
eth0 instead of enp11s0, but hadn't tried this before things broke.  According 
to the man page eth0 is the default, but I can't recall manually specifying a 
different interface for ifplugd in the past.  It always brought up the wired 
interface, no matter what it was called.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Alan McKinnon]

On 21/12/2015 19:21, Peter Humphrey wrote:
> On Monday 21 December 2015 14:06:25 James wrote:
> 
>> H. I would think most folks running openrc are also not using udev
>> but are using eudev [1]? From what I read/understand openrc is in the
>> process of removal from @system, for all profiles?
> 
> I don't know about that, but I'm certainly using udev with openrc.
> 
> While I'm here, is there any practical difference between world and @world, 
> or between system and @system?
> 


There are no differences in practice, it's a semantic thing.

Portage used "emerge world" from the very beginning (lifted from FreeBSD
ports) and it's still supported today even though technically and
semantically "emerge @world" is more correct - world is at heart a set.

It's mentioned in one of portage's man pages, IIRC in emerge (1) but
right now I don't have the inclination to look. That is left as an
exercise for the interested reader.



-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[waltdnes]

On Mon, Dec 21, 2015 at 02:06:25PM +, James wrote

> From what I read/understand openrc is in the process of removal from
> @system, for all profiles?

  In Lennart's dreams... and many peoples' nightmares.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Alan McKinnon]

On 21/12/2015 16:06, James wrote:
> Mick  gmail.com> writes:
> 
> 
> 
> 
 In addition /var/log/rc.log is empty - no messages are captured,
 Finally, there are a lot of messages like this in the console at boot
 time:
> 
 * start-stop-daemon: fopen 'var/run/dbus.pid' : No such file or 
 directory Detaching to start '/usr/bin/dbus-daemon ...'
 * runscript is deprecated; please use openrc-run instead.
 How do I put this right?
> 
> H. I would think most folks running openrc are also not using udev
> but are using eudev [1]? From what I read/understand openrc is in the
> process of removal from @system, for all profiles?


I would wager the opposite. eudev was a temporary hack - udev with stuff
removed.

I use openrc everywhere with udev, and have never run eudev at all



-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Mick]

On Tuesday 22 Dec 2015 00:48:13 Neil Bothwick wrote:
> On Mon, 21 Dec 2015 23:55:06 +, Mick wrote:
> > > Are you trying to run ifplugd from its init script? It's not meant to
> > > be used like that with openrc.
> > 
> > I don't have any init scripts for ifplugd.  I wondered what starts
> > it/stops it, and found /lib64/netifrc/net/ifplugd.sh
> 
> It should be started by the net.eth* scripts, so you need to start the
> network interface first.

Thanks again Neil.  I don't think this is as you suggest.  I never had wired 
or wireless interfaces enabled to start at boot time, because ifplugd started 
them up as necessary.

From the README file:

   The network interface which is controlled by ifplugd should not be
   configured automatically by your distribution's network subsystem,
   since ifplugd will do this for you if needed.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Kai Krakow]

Am Mon, 21 Dec 2015 22:37:38 +
schrieb Mick :

> On Monday 21 Dec 2015 21:43:00 Kai Krakow wrote:
> > Am Mon, 21 Dec 2015 16:25:34 -0500
> > 
> > schrieb waltd...@waltdnes.org:
> > > On Mon, Dec 21, 2015 at 02:06:25PM +, James wrote
> > > 
> > > > From what I read/understand openrc is in the process of removal
> > > > from @system, for all profiles?
> > > > 
> > >   In Lennart's dreams... and many peoples' nightmares.
> > 
> > Haters gonna hate...
> > 
> > If I look at the virtual/service-manager ebuild, openrc probably in
> > the process of being removed from the system set and replaced by
> > this virtual. In that way you can more easily replace openrc with a
> > service manager of your choice.
> > 
> > The upgrade path will be straight forward: It doesn't affect your
> > openrc installation at all because through the service-manager deps
> > openrc is still pulled into the system set - simply by the fact
> > that it is installed.
> 
> Nevertheless, virtual options to make it easier to use alternatives
> to the current stable version of openrc are not my problem at this
> stage.  I can't get ifplugd to work, unless I start up net.
> first and I am getting no /var/log/rc.log to see what's gone
> sideways.  Regardless of these problems I am getting warnings on the
> console during boot time as posted initially.

Apparently I cannot help here because I removed openrc from my system
months ago (even install masking /etc/init.d) but I still maintain
systems which run openrc (and, *cough* baselayout-1, you didn't read
that, did you?). Upgrade paths there almost always involved following
"eselect news read new", the hardest ones involved network and device
management services. It's kind of a challenge to do this on a headless,
remote system without needing to physically access the machine. [1]

> 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

Hehe... Hey, this is surprisingly amusing. May I quote that? :-D
Thanks for the smirk.


[1]: Ah well, I cheated a bit: It's virtualized so I had another
channel of console access. ;-)

-- 
Regards,
Kai

Replies to list-only preferred.


signature.asc
Description: PGP signature

[gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Kai Krakow]

Am Mon, 21 Dec 2015 23:20:24 +
schrieb Mick :

> 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.


signature.asc
Description: PGP signature

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Mick]

On Monday 21 Dec 2015 23:35:21 Neil Bothwick wrote:
> On Mon, 21 Dec 2015 23:20:24 +, Mick wrote:
> > localmount works and I see no failures in mounting my filesystems.
> > What fails repeatably is ifplugd, which no longer starts wired or
> > wireless devices.
> 
> Are you trying to run ifplugd from its init script? It's not meant to be
> used like that with openrc.

I don't have any init scripts for ifplugd.  I wondered what starts it/stops 
it, and found /lib64/netifrc/net/ifplugd.sh
.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Kai Krakow]

Am Mon, 21 Dec 2015 23:41:08 +
schrieb Mick :

>  *   Skipping module netplugd due to missing program: /sbin/netplugd

Could it be that sys-apps/netplug is what you want to use now instead
of ifplugd?

Did you try it? I think I remember that ifplugd simply did no longer
reliably work with younger baselayout and openrc (at least before I
abandoned it in favor of another service manager).

-- 
Regards,
Kai

Replies to list-only preferred.


signature.asc
Description: PGP signature

[gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[»Q«]

On Mon, 21 Dec 2015 21:40:30 +
Neil Bothwick  wrote:

> On Mon, 21 Dec 2015 16:25:34 -0500, waltd...@waltdnes.org wrote:
> 
> > > From what I read/understand openrc is in the process of removal
> > > from @system, for all profiles?
> > 
> >   In Lennart's dreams... and many peoples' nightmares.  
> 
> It's got nothing to do with Lennart. There is a choice of init
> managers, openrc or systemd - so portage should, and apparently will,
> handle this with a virtual. Currently, openrc is forced on those
> using systemd, even though they have no use for it - that is just as
> wrong as forcing systemd on openrc users.

AFAICT, the day is pretty close.


and  indicate openrc is
still in @system as a stopgap, to keep providing functions.sh because
of bugs 373219 (FIXED already) and
, which only has 4
ebuilds left to fix.

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Mick]

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.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Kai Krakow]

Am Mon, 21 Dec 2015 16:59:39 -0600
schrieb »Q« :

> On Mon, 21 Dec 2015 21:40:30 +
> Neil Bothwick  wrote:
> 
> > On Mon, 21 Dec 2015 16:25:34 -0500, waltd...@waltdnes.org wrote:
> > 
> > > > From what I read/understand openrc is in the process of removal
> > > > from @system, for all profiles?
> > > 
> > >   In Lennart's dreams... and many peoples' nightmares.  
> > 
> > It's got nothing to do with Lennart. There is a choice of init
> > managers, openrc or systemd - so portage should, and apparently
> > will, handle this with a virtual. Currently, openrc is forced on
> > those using systemd, even though they have no use for it - that is
> > just as wrong as forcing systemd on openrc users.
> 
> AFAICT, the day is pretty close.
> 
> 
> and  indicate openrc
> is still in @system as a stopgap, to keep providing functions.sh
> because of bugs 373219 (FIXED already) and
> , which only has 4
> ebuilds left to fix.

Fixed here by install masking /etc/init.d and symlinking functions.sh
to the new location. ;-)

Disclaimer: Do not apply on openrc systems.

-- 
Regards,
Kai

Replies to list-only preferred.

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Neil Bothwick]

On Mon, 21 Dec 2015 23:20:24 +, Mick wrote:

> localmount works and I see no failures in mounting my filesystems.
> What fails repeatably is ifplugd, which no longer starts wired or
> wireless devices.

Are you trying to run ifplugd from its init script? It's not meant to be
used like that with openrc.


-- 
Neil Bothwick

I distinctly remember forgetting that.


pgpcygyspmfHk.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Neil Bothwick]

On Mon, 21 Dec 2015 23:55:06 +, Mick wrote:

> > Are you trying to run ifplugd from its init script? It's not meant to
> > be used like that with openrc.  
> 
> I don't have any init scripts for ifplugd.  I wondered what starts
> it/stops it, and found /lib64/netifrc/net/ifplugd.sh

It should be started by the net.eth* scripts, so you need to start the
network interface first.


-- 
Neil Bothwick

Pound for pound, the amoeba is the most vicious animal on the earth.


pgprzWTEjKBdl.pgp
Description: OpenPGP digital signature

[gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Kai Krakow]

Am Tue, 22 Dec 2015 00:54:35 +
schrieb Mick :

> On Tuesday 22 Dec 2015 00:48:13 Neil Bothwick wrote:
> > On Mon, 21 Dec 2015 23:55:06 +, Mick wrote:
> > > > Are you trying to run ifplugd from its init script? It's not
> > > > meant to be used like that with openrc.
> > > 
> > > I don't have any init scripts for ifplugd.  I wondered what starts
> > > it/stops it, and found /lib64/netifrc/net/ifplugd.sh
> > 
> > It should be started by the net.eth* scripts, so you need to start
> > the network interface first.
> 
> Thanks again Neil.  I don't think this is as you suggest.  I never
> had wired or wireless interfaces enabled to start at boot time,
> because ifplugd started them up as necessary.
> 
> From the README file:
> 
>The network interface which is controlled by ifplugd should not be
>configured automatically by your distribution's network subsystem,
>since ifplugd will do this for you if needed.

But that doesn't apply here because the "net.* plugin" starts ifplugd,
and defers further initializations until ifplugd detects a link.

This is what I meant when I talked about pushing ifplugd further down
the layer. I just didn't remember that this is now solved by a plugin
in net.* itself.

Don't enable ifplugd service. Openrc will do its magic.

-- 
Regards,
Kai

Replies to list-only preferred.


signature.asc
Description: PGP signature

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Mick]

On Monday 21 Dec 2015 21:43:00 Kai Krakow wrote:
> Am Mon, 21 Dec 2015 16:25:34 -0500
> 
> schrieb waltd...@waltdnes.org:
> > On Mon, Dec 21, 2015 at 02:06:25PM +, James wrote
> > 
> > > From what I read/understand openrc is in the process of removal from
> > > @system, for all profiles?
> > > 
> >   In Lennart's dreams... and many peoples' nightmares.
> 
> Haters gonna hate...
> 
> If I look at the virtual/service-manager ebuild, openrc probably in
> the process of being removed from the system set and replaced by this
> virtual. In that way you can more easily replace openrc with a service
> manager of your choice.
> 
> The upgrade path will be straight forward: It doesn't affect your openrc
> installation at all because through the service-manager deps openrc is
> still pulled into the system set - simply by the fact that it is
> installed.

Nevertheless, virtual options to make it easier to use alternatives to the 
current stable version of openrc are not my problem at this stage.  I can't 
get ifplugd to work, unless I start up net. first and I am getting no 
/var/log/rc.log to see what's gone sideways.  Regardless of these problems I 
am getting warnings on the console during boot time as posted initially.

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

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Mick]

On Monday 21 Dec 2015 23:20:24 Mick wrote:
> 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.

I got rc.log going.  Attached, in case you can spot something amiss.  Please 
note wlan0 NIC was switched off at the time.

-- 
Regards,
Mick


rc boot logging started at Mon Dec 21 23:21:54 2015

 * Loading module i2c-dev ...
 [ ok ]
 * Autoloaded 1 module(s)
 * Checking local filesystems  ...
root: clean, 258811/673296 files, 1815499/2688871 blocks
boot: clean, 64/12048 files, 42672/48160 blocks
home: clean, 55366/1281120 files, 3053874/5120710 blocks
 [ ok ]
 * Remounting root filesystem read/write ...
 [ ok ]
 * Remounting filesystems ...
 [ ok ]
 * Updating /etc/mtab ...
 * Creating mtab symbolic link
 [ ok ]
 * runscript is deprecated; please use openrc-run instead.
 * Use of the opts variable is deprecated and will be
 * removed in the future.
 * Please use extra_commands, extra_started_commands or extra_stopped_commands.
 * Invalidating stale software suspend images ...
 [ ok ]
 * Activating swap devices ...
 [ ok ]
 * Mounting local filesystems ...
 [ ok ]
 * Configuring kernel parameters ...
* Applying /etc/sysctl.conf ...
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
 [ ok ]
 * Creating user login records ...
 [ ok ]
 * Wiping /tmp directory ...
 [ ok ]
 * runscript is deprecated; please use openrc-run instead.
 * Restoring Mixer Levels ...
 [ ok ]
 * Mounting misc binary format filesystem ...
 [ ok ]
 * Loading custom binary format handlers ...
 [ ok ]
 * Setting terminal encoding [UTF-8] ...
 [ ok ]
 * Setting console font [default8x16] ...
 [ ok ]
 * Setting hostname to dell_xps ...
 [ ok ]
 * Setting keyboard mode [UTF-8] ...
 [ ok ]
 * Loading key mappings [uk] ...
 [ ok ]
 * Bringing up network interface lo ...
 [ ok ]
 * runscript is deprecated; please use openrc-run instead.
 * Updating microcode ...
 [ ok ]
 * runscript is deprecated; please use openrc-run instead.
 * Bringing up interface lo
 *   Skipping module adsl due to missing program: /usr/sbin/adsl-start /usr/sbin/pppoe-start
 *   Skipping module br2684ctl due to missing program: br2684ctl
 *   Skipping module bridge due to missing program: brctl
 *   Skipping module clip due to missing program: /usr/sbin/atmsigd
 *   Skipping module netplugd due to missing program: /sbin/netplugd
 *   Skipping module ipppd due to missing program: /usr/sbin/ipppd
 *   Skipping module firewalld due to missing program: firewall-cmd
 *   Skipping module dhclient due to missing program: /sbin/dhclient
 *   Skipping module pump due to missing program: /sbin/pump
 *   Loaded modules: apipa arping bonding tuntap ccwgroup ethtool macvlan macchanger macnet ifplugd wpa_supplicant ssidnet iproute2 pppd system vlan dhcpcd ip6rd ip6to4
 *   ifplugd only works on interfaces with a valid MAC address
 *   127.0.0.1/8 ...
 [ ok ]
 *   Adding routes
 * 127.0.0.0/8 via 127.0.0.1 ...
 [ ok ]
 * Activating additional swap space ...
 [ ok ]
 * Setting up tmpfiles.d entries ...
 [ ok ]
 * Initializing random number generator ...
 [ ok ]

rc boot logging stopped at Mon Dec 21 23:21:58 2015


rc default logging started at Mon Dec 21 23:21:58 2015

 * runscript is deprecated; please use openrc-run instead.
 * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
 [ ok ]
 * Starting syslog-ng ...
 * start-stop-daemon: fopen `/run/syslog-ng.pid': No such file or directory
 * Detaching to start `/usr/sbin/syslog-ng' ...
 [ ok ]
 * runscript is deprecated; please use openrc-run instead.
Arno's Iptables Firewall Script v2.0.1e
---
Platform: Linux 4.1.12-gentoo x86_64
WARNING: External interface ppp0 does NOT exist (yet?)
Checking/probing Iptables modules:
[snip ...]

Dec 21 23:22:04 All firewall rules applied.
 * runscript is deprecated; please use openrc-run instead.
 * Starting chronyd ...
 * 

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Mick]

On Monday 21 Dec 2015 23:49:02 Kai Krakow wrote:
> Am Mon, 21 Dec 2015 23:20:24 +
> 
> schrieb Mick :
> > 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.

ifplugd does not have a debug mode, but starting it by hand I see this:

Dec 22 00:38:08 dell_xps ifplugd(eth0)[4982]: ifplugd 0.28 initializing.
Dec 22 00:38:08 dell_xps ifplugd(eth0)[4982]: Using interface eth0
Dec 22 00:38:08 dell_xps ifplugd(eth0)[4982]: Failed to detect plug status of 
eth0
Dec 22 00:38:08 dell_xps ifplugd(eth0)[4982]: Exiting.

Ha!  It now assumes that I have an eth0 interface, which I don't.  Hmm ...  I 
wonder where it reads this from.

If I start the NIC manually I get:

Dec 22 00:33:52 dell_xps kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp11s0: link 
becomes ready
Dec 22 00:35:31 dell_xps kernel: IPv6: ADDRCONF(NETDEV_UP): enp11s0: link is 
not ready
Dec 22 00:35:30 dell_xps ifplugd(enp11s0)[4293]: ifplugd 0.28 initializing.
Dec 22 00:35:30 dell_xps ifplugd(enp11s0)[4293]: Using interface 
enp11s0/00:26:B9:20:B4:9C with driver  (version: 3.137)
Dec 22 00:35:30 dell_xps ifplugd(enp11s0)[4293]: Using detection mode: 
SIOCETHTOOL


> 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.

Yes, ifplugd is needed here.  Otherwise removal/insertion of the ethernet 
cable does not bring up/down the enp11s0 interface.


> 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.

Thank you for pointing me in this direction.  If ifplud now thinks that eth0 
is the default interface, where might it be deducing this from?  I installed 
sys-fs/udev-225 and dev-libs/libgudev-230 at the same time I updated openrc 
and this is when the problems started.

I never had an ifplugd.conf in use, perhaps I ought to set up one now?


> 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. :-)

Thank you for this suggestion, but for reasons covered exhaustively and 
exhaustingly in a few past mega-threads I'd rather stay with openrc.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[James]

Mick  gmail.com> writes:




> > > In addition /var/log/rc.log is empty - no messages are captured,
> > > Finally, there are a lot of messages like this in the console at boot
> > > time:

> > > * start-stop-daemon: fopen 'var/run/dbus.pid' : No such file or 
> > > directory Detaching to start '/usr/bin/dbus-daemon ...'
> > > * runscript is deprecated; please use openrc-run instead.
> > > How do I put this right?

H. I would think most folks running openrc are also not using udev
but are using eudev [1]? From what I read/understand openrc is in the
process of removal from @system, for all profiles?



> > I think your error is related to my thread below.
> > Just get rid of line form fstab:
> > none /proc proc defaults 0 0
> > and any other not related ones.
> Thank you Thelma, but I do not have /proc or /tmpfs on my stab.  Just a  
> few  disk partitions.


Another thread alluded to a news post. I cannot find that old news post?

I use a simple partition scheme with /boot  /  and /usr/local on separate
partitions. So the consensus is remove both of these from the fstab?::

shm /dev/shm tmpfs   nodev,nosuid,noexec  0 0

none/procprocdefaults 0 0


Historically speaking, fstab, mtab init* and cgroups were all very well
defined and mostly logical to figure out and follow. Where do I read up on
the mtab functionality, particularly in light of these dynamic changes and
as inter-related issue between where openrc, mount, fstab and mtab will end
up, functionally, in the future gentoo scheme?  


James

[1] https://wiki.gentoo.org/wiki/Eudev

[gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Kai Krakow]

Am Tue, 22 Dec 2015 00:50:24 +
schrieb Mick :

> > 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.  
> 
> ifplugd does not have a debug mode, but starting it by hand I see
> this:
> 
> Dec 22 00:38:08 dell_xps ifplugd(eth0)[4982]: ifplugd 0.28
> initializing. Dec 22 00:38:08 dell_xps ifplugd(eth0)[4982]: Using
> interface eth0 Dec 22 00:38:08 dell_xps ifplugd(eth0)[4982]: Failed
> to detect plug status of eth0
> Dec 22 00:38:08 dell_xps ifplugd(eth0)[4982]: Exiting.
> 
> Ha!  It now assumes that I have an eth0 interface, which I don't.
> Hmm ...  I wonder where it reads this from.

man ifplugd ;-)

-- 
Regards,
Kai

Replies to list-only preferred.


signature.asc
Description: PGP signature

Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd

[Peter Humphrey]

On Monday 21 December 2015 14:06:25 James wrote:

> H. I would think most folks running openrc are also not using udev
> but are using eudev [1]? From what I read/understand openrc is in the
> process of removal from @system, for all profiles?

I don't know about that, but I'm certainly using udev with openrc.

While I'm here, is there any practical difference between world and @world, 
or between system and @system?

-- 
Rgds
Peter