On Sat, 26 Jul 2014, Zenaan Harkness wrote: > Interrelated problem A: > $ ps aux|egrep -i acpid > root 318 0.0 0.0 0 0 ? S< 12:40 0:00 [ktpacpid] > root 19855 0.0 0.0 4372 972 ? Ss 17:45 0:00 > /usr/sbin/acpid > $ sudo systemctl stop acpid > Job for acpid.service canceled. > $ ps aux|egrep -i acpid > root 318 0.0 0.0 0 0 ? S< 12:40 0:00 [ktpacpid] > root 19960 0.0 0.0 4372 972 ? Ss 17:46 0:00 > /usr/sbin/acpid
acpid was restarted after you stopped it. Since just about everything in a "modern desktop" will pester the acpi netlink socket, please ask a systemd expert whether "systemctl stop" *blocks* socket activation of that service until further notice, or not. If it doesn't block socket activation, then we have a grave problem in the systemd invoke-rc.d interface. The semanthics for invoke-rc.d stop is that the service must NOT be restarted automatically until it is manually restarted by the admin or by invoke-rc.d. These semanthics are *required* for proper package upgrades/downgrades. Note that a direct call to systemctl does count as "manual invocation by the admin". -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140726174430.gb30...@khazad-dum.debian.net
