Description of problem: NetworkManager-dispatcher.service is enabled, but does not run after computer boots: $ systemctl status NetworkManager-dispatcher.service NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled) Active: inactive (dead) since Mon 2013-07-15 07:51:52 CEST; 9s ago Process: 787 ExecStart=/usr/libexec/nm-dispatcher.action (code=exited, status=0/SUCCESS) The process seems to exit correctly, but I would expect it to be always running and executing scripts from /etc/NetworkManager/dispatcher.d/ on network changes. I can start the service manually and then the process is running. But I reboot or suspend/resume the machine, the process will have exited again. This worked correctly on Fedora 18, the dispatcher process was running all the time - after boot and after resume. Version-Release number of selected component (if applicable): NetworkManager-0.9.8.2-8.git20130709.fc19.x86_64 How reproducible: always Steps to Reproduce: 1. enable NetworkManager-dispatcher.service 2. reboot 3. see its status, it's exited
Created attachment 773588 [details] journal after boot
I tried in a freshly installed VM (I had to enable and start the service). After boot, the process seems to be running, for a while, then it exits: [root@localhost ~]# systemctl status NetworkManager-dispatcher.service NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled) Active: active (running) since Mon 2013-07-15 08:00:38 EDT; 10s ago Main PID: 397 (nm-dispatcher.a) CGroup: name=systemd:/system/NetworkManager-dispatcher.service └─397 /usr/libexec/nm-dispatcher.action [root@localhost ~]# systemctl status NetworkManager-dispatcher.service NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled) Active: inactive (dead) since Mon 2013-07-15 08:00:52 EDT; 59s ago Process: 397 ExecStart=/usr/libexec/nm-dispatcher.action (code=exited, status=0/SUCCESS)
I learned from jklimes that this is an expected behavior: <jklimes> kparal: the dispatcher is not supposed to be running all the time. Rather it runs on an event (e.g. connection up) do the work and keeps running for 10s and exits. <jklimes> kparal: it has a command line --persist to keep it running all the time <jklimes> for debugging you can use: /usr/libexec/nm-dispatcher.action --persist --debug I got confused because in F18 I believe the process was running all the time. Never mind, sorry for the noise. Closing as NOTABUG.