From: thelma@sys-concept.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with openrc-0.18.4 and ifplugd
Date: Sun, 20 Dec 2015 18:29:44 -0700 [thread overview]
Message-ID: <56775608.3090208@sys-concept.com> (raw)
In-Reply-To: <201512201826.31348.michaelkintzios@gmail.com>
Thelma
On 12/20/2015 11:26 AM, Mick wrote:
> Two laptops will not bring up their wired/wireless interface(s) since the
> upgrade to the latest stable openrc. Interfaces have to be started manually,
> after which ifplugd starts on its own:
> =====================================
>
> /etc/init.d/net.enp11s0 start
> * Bringing up interface enp11s0
> * 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
> * Configuring enp11s0 for MAC address 00:26:B9:20:B4:9C ... [
> ok ]
> * Starting ifplugd on enp11s0 ...
> * start-stop-daemon: fopen `/var/run/ifplugd.enp11s0.pid': No such file or
> directory
> * Detaching to start `/usr/sbin/ifplugd' ... [
> ok ]
> * Backgrounding ...
> * WARNING: net.enp11s0 has started, but is inactive
> ====================================================
>
>
> 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?
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.
Thelma
next prev parent reply other threads:[~2015-12-21 1:29 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 [this message]
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
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=56775608.3090208@sys-concept.com \
--to=thelma@sys-concept.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