After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 691102 - signals like SIGINT and SIGTERM should be properly handled
signals like SIGINT and SIGTERM should be properly handled
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-01-03 23:59 UTC by Pavel Simerda
Modified: 2020-11-12 14:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pavel Simerda 2013-01-03 23:59:29 UTC
Steps to reproduce:

1) Check that NetworkManager and dhclient are not running

2) Run NetworkManager --no-daemon

3) Stop it using ctrl+c

Expected result:

dhclient is not running

Actual result:

dhclient is running
Comment 1 Pavel Simerda 2013-01-04 00:04:30 UTC
Replace step #3 with 'killall NetworkManager' from another screen and the result is the same.
Comment 2 Pavel Simerda 2013-05-06 16:32:14 UTC
Administrators and tools can send signals to the NetworkManager daemon:

SIGKILL

Behavior of this one cannot be altered. NetworkManager is simply killed and any child processes remain running unless they can detect the lost parent. Child processes should try to detect that (e.g. via broken dbus link) and exit.

SIGTERM
SIGQUIT (ctrl+\)

Developers could use ctrl+\ to trigger the same behavior as regular stopping the NetworkManager while killing all child processes first.

SIGINT (ctrl+c)

Developers could use ctrl+c to stop NetworkManager and let it disconnect all connections first (killing the child processes of course).

That way the behavior would be more useful for developers (choice between ctrl+c and ctrl+\) and also better for administrators (no processes left over when running e.g. killall NetworkManager or service NetworkManager stop).
Comment 3 André Klapper 2020-11-12 14:30:43 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).