Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 761993 - sys-apps/ifplugd unwanted default behavior
Summary: sys-apps/ifplugd unwanted default behavior
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
Depends on:
Reported: 2020-12-27 20:43 UTC by Another Mortal
Modified: 2020-12-27 22:48 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Another Mortal 2020-12-27 20:43:13 UTC
The current ebuild forcibly removes the default initscript `/etc/init.d/ifplugd` in favor of default handling by `net-misc/netifrc`.  I find that odd, since people _may_ want to opt for a different behavior, closer to what was originally intended.  In that case, having access to the original initscript could prove convenient.

Unfortunately, that default behavior renders `ifplugd` completely useless for my target scenario, since bringing down the wired interface also stops `ifplugd` on said inteface; but the whole point of using `ifplugd` would be to bring that interface back up, once the cable is [re]connected.

I tried disabling the relevant `netifrc` module by setting `modules='!plug'` in `/etc/conf.d/net` to no avail. (See separate bug report:  As long as the PID file `/var/run/` exists, `netifrc` will stop `ifplugd`.

The only workaround I found was to manually delete the PID file.  That stops `netifrc` from interfering, and let's `ifplugd` keep running.

Reproducible: Always