[Pkg-utopia-maintainers] Bug#745029: Bug#745029: network-manager: automatically kills scripts that take longer than 3 seconds

[MAG4 Piemonte]

Dear Michael and Dan, thank you for the answers.
So we will wait NM next versions to test the restore of the symlink ...
Regards!

Guido

In data lunedì 19 maggio 2014 12:01:39, Dan Williams ha scritto:
> On Mon, 2014-05-19 at 17:05 +0200, Michael Biebl wrote:
> > Am 17.04.2014 13:13, schrieb MAG4 Piemonte:
> > > Package: network-manager
> > > Version: 0.9.8.8-5
> > > Severity: normal
> > > 
> > > Dear Maintainer,
> > > after upgrading in a Testing machine with systemd to 0.9.8.8-5 version we get
> > > nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' took
> > > too long; killing it.
> > > with no mount of nfs partitions.
> > > Investigating we found
> > > https://wiki.archlinux.org/index.php/NetworkManager#Avoiding_the_three_seconds_timeout
> > > so we replace the symlink /etc/systemd/system/dbus-org.freedesktop.nm-
> > > dispatcher.service creating the script file /etc/systemd/system/dbus-
> > > org.freedesktop.nm-dispatcher.service with the following content:
> > >   .include /lib/systemd/system/NetworkManager-dispatcher.service
> > >   [Service]
> > >   RemainAfterExit=yes
> > > and enable the script file with permissions rwxr-xr-x.
> > > Doing so we workaroud the problem ...
> > > Regards!
> > > 
> > 
> > 
> > That is intended behaviour. Scripts are not supposed to start long
> > running tasks. Please fix your scripts to not do that.
> > 
> > Afaics there is nothing to fix on the NM side, right Dan?
> 
> At the moment it's intended behavior.  NM 0.9.9+ have bumped the timeout
> to 20 seconds, and for 0.9.10 we're planning to make NetworkManager
> block on dispatcher scripts for up/down.  Obviously, that makes your
> network connections take longer to connect or disconnect if the
> dispatcher scripts are stupid, but then the stupid scripts need to get
> fixed to not take so long.
> 
> Note that for NFS especially, network connections can drop without
> warning, especially on WWAN/WiFi/Bluetooth, and at that point the
> connection is completely gone, and NFS just has to handle that without
> blocking.
> 
> Dan
>