From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd
Date: Tue, 22 Dec 2015 14:04:12 +0000 [thread overview]
Message-ID: <201512221404.21979.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20151222021210.1ff51a89@jupiter.sol.kaishome.de>
[-- Attachment #1: Type: Text/Plain, Size: 2950 bytes --]
On Tuesday 22 Dec 2015 01:12:10 Kai Krakow wrote:
> Am Tue, 22 Dec 2015 00:54:35 +0000
>
> schrieb Mick <michaelkintzios@gmail.com>:
> > On Tuesday 22 Dec 2015 00:48:13 Neil Bothwick wrote:
> > > On Mon, 21 Dec 2015 23:55:06 +0000, 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.<iface> 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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-22 14:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 18:26 [gentoo-user] Problem with openrc-0.18.4 and ifplugd Mick
2015-12-21 1:29 ` thelma
2015-12-21 6:15 ` Mick
2015-12-21 14:06 ` [gentoo-user] " James
2015-12-21 17:21 ` Peter Humphrey
2015-12-21 20:33 ` Alan McKinnon
2015-12-21 20:30 ` Alan McKinnon
2015-12-21 21:25 ` waltdnes
2015-12-21 21:40 ` Neil Bothwick
2015-12-21 22:59 ` »Q«
2015-12-21 23:18 ` Kai Krakow
2015-12-21 21:43 ` Kai Krakow
2015-12-21 22:37 ` Mick
2015-12-21 22:38 ` Alan McKinnon
2015-12-21 23:20 ` Mick
2015-12-21 23:35 ` Neil Bothwick
2015-12-21 23:55 ` Mick
2015-12-22 0:48 ` Neil Bothwick
2015-12-22 0:54 ` Mick
2015-12-22 1:12 ` Kai Krakow
2015-12-22 14:04 ` Mick [this message]
2015-12-22 14:20 ` Kai Krakow
2015-12-22 15:15 ` Mick
2015-12-22 23:32 ` Neil Bothwick
2015-12-23 10:58 ` Mick
2015-12-21 23:41 ` Mick
2015-12-21 23:54 ` Kai Krakow
2015-12-21 23:49 ` Kai Krakow
2015-12-22 0:50 ` Mick
2015-12-22 1:12 ` Kai Krakow
2015-12-21 22:54 ` Kai Krakow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201512221404.21979.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox