Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 370687 - sys-apps/openrc restarts all net dependent services on ppp reconnect
Summary: sys-apps/openrc restarts all net dependent services on ppp reconnect
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: OpenRC (show other bugs)
Hardware: All Linux
: Normal major
Assignee: OpenRC Team
URL:
Whiteboard: openrc:oldnet
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-08 14:48 UTC by Moritz Bechler
Modified: 2013-04-25 23:08 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Bechler 2011-06-08 14:48:52 UTC
sys-apps/openrc-0.8.2-r1: OpenRC seems to restart all net dependend services when net.ppp0 reconnects. This might be essential for services binding to that interface but this also kills all services running on other interfaces (which imho is the more widespread case).
That is really annoying in our case as the affected services include openafs-client (which typically won't restart cleanly) and openldap (beeing the nss backend for our desktops).


I tried to fix that by putting
rc_net_ppp0_provide="!net"
into /etc/rc.conf (will report tomorrow whether this worked or not).

Generally I would consider this behaviour a really bad default (also inconsistent with the baselayout-1 behaviour). Imho the restarts should only be triggered by default when the last interface goes down.




Reproducible: Always
Comment 1 Moritz Bechler 2011-06-09 15:35:52 UTC
ok,

rc_net_ppp0_provide="!net"

seems to work for me. Still this isn't a sane default and propably not only related to ppp, think about wifi for example.
Comment 2 SpanKY gentoo-dev 2011-06-11 23:52:26 UTC
sounds like you want to be tweaking rc.conf:rc_depend_strict to NO
Comment 3 William Hubbs gentoo-dev 2011-09-02 07:49:01 UTC
There has been no activity on this bug in 3 months.

I am resolving it as INVALID, because it appears to have been a
configuration issue with nothing for us to fix.

If anyone mdisagrees, please feel free to reopen.