Created attachment 289525 [details] netplug.patch Hi, Since sys-apps/netplug-1.2.9.2 the installed configuration file is named /etc/netplug.d/netplug.2 instead of /etc/netplug.d/netplug It seems that netplug do not find it with that name. It looks for /etc/netplug.d/netplug instead (which is not present inside the directory) Here is the log: Oct 11 07:54:40 tatooine kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Oct 11 07:54:40 tatooine kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Oct 11 07:54:40 tatooine netplugd[23517]: eth0: state DOWN flags 0x00001003 UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 Oct 11 07:54:40 tatooine netplugd[23626]: /etc/netplug.d/netplug eth0 in -> pid 23626 Oct 11 07:54:40 tatooine netplugd[23626]: /etc/netplug.d/netplug: No such file or directory Oct 11 07:54:40 tatooine netplugd[23517]: eth0: state INNING pid 23626 exited status 256 Renaming the file /etc/netplug.d/netplug.2 to /etc/netplug.d/netplug fixes this: Oct 11 07:55:46 tatooine kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Oct 11 07:55:46 tatooine netplugd[16411]: eth0: state DOWN flags 0x00001003 UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 Oct 11 07:55:46 tatooine netplugd[19593]: /etc/netplug.d/netplug eth0 in -> pid 19593 Oct 11 07:55:47 tatooine /etc/init.d/net.eth0[19719]: No configuration specified; defaulting to DHCP Oct 11 07:55:47 tatooine dhcpcd[19727]: version 5.2.12 starting According to the manpage, this script name seems to be fixed and cannot be changed. Please find attached a small patch that fixes this.
+*netplug-1.2.9.2-r1 (11 Oct 2011) + + 11 Oct 2011; Lars Wendler <polynomial-c@gentoo.org> -netplug-1.2.9.2.ebuild, + +netplug-1.2.9.2-r1.ebuild, +files/netplug-2, -files/netplug.2: + Fixed installation of netplug-2 config file. Thanks to Guillaume Castagnino + who reported this in bug #386733. + What a stupid mistake from me. I'm deeply sorry for the trouble I might have caused by this...
*** Bug 386761 has been marked as a duplicate of this bug. ***