From this week's Distrowatch. Could be a problem in some circumstances.
One of the most recent changes to systemd (available in version 230), forces user processes to terminate when the user logs out. On some systems, such behaviour makes sense and effectively cleans up misbehaving processes when the user leaves. However, many administrators and developers rely on processes continuing to run to perform tests, backups or other tasks after they log off.
I’m still not sure exactly what the problem is. I normally use setsid(1) <http://linux.die.net/man/1/setsid> if I want to run such background processes, and I think this will still work. I asked on this bug report <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394> whether this is the case, but it appears my question has got lost in the usual anti-systemd noise...
Since systemd is generating quite some interest, I've turned the meetup suggestion for systemd into the topic for our meeting in June: http://www.meetup.com/WaikatoLinuxUsersGroup/events/231330392/ Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, NZ +64 (7) 858-5174 http://www.cms.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/