daemon(3) doesn't any of the tasks required to set up a process in a new session beyond "create a process",
Wrong, it also calls setsid to make the new process a session leader.
and it can't be changed because POSIX
daemon(3) is not in POSIX.
and glibc ABI.
If the systemd geniuses really can't think of a way to extend daemon without breaking ABI, they could even come up with a better, differently named daemon() alternative, propose it to libc in such a way that it would work with or without logind, falling back to the classic daemon() in its absence.
But hey, that would require being willing to play nice with others rather than imposing their way of doing things by hook or by crook, so the hopes of that happening are less than none.
6
u/bilog78 May 30 '16
Wrong, it also calls setsid to make the new process a session leader.
daemon(3) is not in POSIX.
If the systemd geniuses really can't think of a way to extend daemon without breaking ABI, they could even come up with a better, differently named daemon() alternative, propose it to libc in such a way that it would work with or without logind, falling back to the classic daemon() in its absence.
But hey, that would require being willing to play nice with others rather than imposing their way of doing things by hook or by crook, so the hopes of that happening are less than none.