On Wed, Feb 25, 2015 at 2:17 PM, Marc Joliet <mar...@gmx.de> wrote: > Am Wed, 25 Feb 2015 10:33:37 +0000 (UTC) > schrieb Duncan <1i5t5.dun...@cox.net>: > >> But you're king of your own boxes. If you want to run it as a user-level >> service and have it quit when you logout that user, go right ahead. > > Again, it *doesn't* terminate when I log out.
FYI - this behavior is completely configurable - you can enable or disable linger for any particular user. I believe you can also use this to do things like kill screen sessions left behind by a user. I think the default is for systemd to not clean up when a user's session ends, but systemd DOES cleanup with a vengeance when a service ends (so if you're like me and spawn background processes from shell scripts in something like cron.daily then make sure you wait somewhere so that systemd doesn't kill everything when your timer script reaches the end - or you can tell systemd to not do cleanup but I don't think that is a great practice). -- Rich
