"systemctl reload tor" fails. stracing shows that kill(2) returns EPERM. A way I have found to fix/work-around this issue is add CAP_KILL to CapabilityBoundingSet in the tor.service file (see the patch). ● tor.service - The Onion Router Loaded: loaded (/etc/systemd/system/tor.service; disabled) Active: active (running) (Result: exit-code) since sob 2015-03-07 20:01:34 CET; 6min ago Process: 8588 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=1/FAILURE) Main PID: 8481 (tor) CGroup: /system.slice/tor.service └─8481 /usr/bin/tor --RunAsDaemon 0 -f /etc/tor/torrc mar 07 20:01:45 kotik Tor[8481]: Caching new entry tor for tor mar 07 20:01:45 kotik Tor[8481]: Caching new entry tor for tor mar 07 20:01:45 kotik systemd[1]: Reloaded The Onion Router. mar 07 20:01:52 kotik Tor[8481]: Bootstrapped 90%: Establishing a Tor circuit mar 07 20:02:46 kotik Tor[8481]: No circuits are opened. Relaxed timeout for circuit 13 (a Gene...ive. mar 07 20:02:54 kotik Tor[8481]: Tor has successfully opened a circuit. Looks like client funct...ing. mar 07 20:02:54 kotik Tor[8481]: Bootstrapped 100%: Done mar 07 20:07:09 kotik systemd[1]: Reloading The Onion Router. mar 07 20:07:09 kotik systemd[1]: tor.service: control process exited, code=exited status=1 mar 07 20:07:09 kotik systemd[1]: Reload failed for The Onion Router. Reproducible: Always
Created attachment 398320 [details, diff] Add CAP_KILL to the CapabilityBoundingSet
*** This bug has been marked as a duplicate of bug 534014 ***
(In reply to Anthony Basile from comment #2) > > *** This bug has been marked as a duplicate of bug 534014 *** Actually I'm not 100% sure this is a dup. Nonetheless, I think its fixed in 0.2.6.3. Can you please test.
