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: Wed, 23 Dec 2015 10:58:35 +0000 [thread overview]
Message-ID: <201512231058.46162.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20151222233240.4be74cda@digimed.co.uk>
[-- Attachment #1: Type: Text/Plain, Size: 1439 bytes --]
On Tuesday 22 Dec 2015 23:32:40 Neil Bothwick wrote:
> On Tue, 22 Dec 2015 15:15:57 +0000, 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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-23 10:59 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
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 [this message]
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=201512231058.46162.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