> Since the number of commands that start such a process is limited to
> screen/tmux/nohup, these could just be shimmed to do whatever's
> needed to let them keep running past logout.
I think implementing a workaround like that would just confuse the
situation even more. I can easily imagine hours wasted digging around in
/etc trying to figure out why some programs work properly and others don't.
> Course it would make more sense to have a proper API that such programs
> can use themselves.
That's an even worse idea, because then we're making programs work
around systemd's decisions. Interoperability and maintenance nightmare,
not to mention the numerous philosophical objections I could think of.
If this were a badly needed architectural change, it might be worth
considering these ideas. But there's so little benefit to this behaviour
that it's simply not worth making the effort to adapt to.
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
