Tor does not come with a systemd service file. Reproducible: Always
Created attachment 361168 [details, diff] tor-0.2.5.1_alpha.ebuild patch
Created attachment 361170 [details] tor.service
Why? TimeoutStopSec=32 LimitNOFILE=30000 Looks like Arch doesn't set them, while Fedora uses different values :/
systemd related upstream bugs: Add tor.service (for systemd) to upstream package https://trac.torproject.org/projects/tor/ticket/8368 Tor systemd socket activation support https://trac.torproject.org/projects/tor/ticket/8908
Thanks, it explains the Limit, not sure about the timeoutStopSec :/
To quote the manpage: SIGINT Tor clients behave as with SIGTERM; but Tor servers will do a controlled slow shutdown, closing listeners and waiting 30 seconds before exiting. (The delay can be configured with the ShutdownWaitLength config option.)
OK, is LimitNOFILE=30000 enough or does it need anything a bit longer (in real run)? Looks like fedora people are letting it a bit more
30000 is just the number in conf.d/tor, I wasn't consulting the other files when I made it. Now that I look this comment is on https://trac.torproject.org/projects/tor/ticket/8368. "If you want to pick just one ulimit -n, 32768 is a good choice. 4096 is way too low for fast relays."
+*tor-0.2.5.1_alpha-r1 (28 Oct 2013) + + 28 Oct 2013; Pacho Ramos <pacho@gentoo.org> +files/tor.service, + +tor-0.2.5.1_alpha-r1.ebuild: + Add unit file (#488426 by Emery Hemingway) +
*** Bug 517024 has been marked as a duplicate of this bug. ***