Bug#717422: aiccu: let the init script be somewhat useful for NetworkManager users too
On 2013-07-20 20:32 , Maurizio Avogadro wrote: This makes the init script useless for NetworkManager users; by adding to it the LSB headers Should-Start: network-manager This sounds like something sane to do. Should-Stop: network-manager This does not entirely; stopping AICCU (thus giving up IPv6 connectivity) does not always mean you want to disconnect everything, there are networks where even AYIYA won't get out of. That said, tinc might benefit from the Should-Start addition too. OpenVPN already has this setup. [..] The soft dependency should leave the behaviorunchangedfor non-NM users; since the connection is established only once at startup, this behavior should be compatible with the strict policiesenforced by SixXS, which forbid automatic reconnections. Nothing strict about this policy, just think about if you would like it if your servers where connected to in a never ending repeating loop (at the rates of hundreds of connects per second from what we have seen) where the user of that automated restart does not realize that that is happening as something in the background is doing it; or because they think they are ubersmart and monitored some random unrelated thing on the Internet and think that restarting is needed... Please note that the policy is primarily there to protect the server from being overwhelmed with useless requests that would effectively also cause a DoS for other users of that service. The behaviour of too many restarts also indicates that the source of those requests is having a problem that should be properly resolved. Greets, Jeroen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717422: aiccu: let the init script be somewhat useful for NetworkManager users too
Il 22/07/2013 09:43, Jeroen Massar ha scritto: Should-Stop: network-manager This does not entirely; stopping AICCU (thus giving up IPv6 connectivity) does not always mean you want to disconnect everything, there are networks where even AYIYA won't get out of. Doesn't Should-Stop: network-manager only mean that AICCU should be stopped before network-manager, if the latter is present? [1] Thanks Maurizio [1]: http://wiki.debian.org/LSBInitScripts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717422: aiccu: let the init script be somewhat useful for NetworkManager users too
Package: aiccu Version: 20070115-15.1 Severity: wishlist Dear Maintainer, the actual init script LSB headers cause the AICCU client to start earlier than NetworkManager: $ ls -1 /etc/rc2.d/S20* /etc/rc2.d/S20aiccu /etc/rc2.d/S20avahi-daemon /etc/rc2.d/S20bluetooth /etc/rc2.d/S20chrony /etc/rc2.d/S20cpufrequtils /etc/rc2.d/S20cron /etc/rc2.d/S20exim4 /etc/rc2.d/S20kerneloops /etc/rc2.d/S20network-manager [...] Because of that, on typical desktop systems relying on NM, the client starts when no network is available, then fails to resolve the TIC server address and exits: # grep -E '(aiccu|NetworkManager)' /var/log/syslog Jul 20 17:06:03 laptop aiccu[4992]: Couldn't resolve host tic.sixxs.net, service 3874 Jul 20 17:06:03 laptop aiccu[4992]: Couldn't connect to the TIC server tic.sixxs.net Jul 20 17:06:03 laptop aiccu[4992]: Couldn't retrieve first tunnel for the above reason, aborting Jul 20 17:06:03 laptop NetworkManager[5421]: info NetworkManager (version 0.9.8.0) is starting... [...] This makes the init script useless for NetworkManager users; by adding to it the LSB headers Should-Start: network-manager Should-Stop: network-manager the init script should start after NM, therefore the AICCU client should be correctly started at least when an auto connect global system connection profile (i.e. the default Auto eth0) is available, thus enabling NM users to have the tunnel automatically available at startup. The soft dependency should leave the behaviorunchangedfor non-NM users; since the connection is established only once at startup, this behavior should be compatible with the strict policiesenforced by SixXS, which forbid automatic reconnections. The only side effect would be that NM users not wanting to have the client started at every boot will have to disable AICCU_ENABLED in /etc/default/aiccu and will therefore be prevented to start the client with invoke-rc.d or running the init script directly. Thanks Maurizio Avogadro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
