On Tue, Feb 11, 2014 at 09:52:51PM +0000, Colin Watson wrote: > On Tue, Feb 11, 2014 at 10:18:52PM +0200, Uoti Urpala wrote: > > And if it's a meaningful sanity check for sshd in particular, then it > > looks like something that should be added to the binary rather than be > > run as a separate shell check. > > Well, of course it is already done in the binary by way of libc's > daemon(), it's just that the error message is dreadful. :-) It hasn't > been *that* important to me so I just went for the lowest-maintenance > approach rather than refining it; I've already spent more time > discussing it in this thread than I spent maintaining it in the last six > years. > > Again, yeah, it probably ought to be done in the binary and upstreamed > etc., I've just had better things to do. I don't mind if somebody feels > the need to chase this upstream.
After all this, I just did some more testing and realised that the check is entirely irrelevant for the upstart and systemd cases, because it's there to avoid a confusing failure mode from the libc daemon() function, and of course daemon() isn't called when we run with -D! So I'm removing the check from those job/service files for my next upload. -- Colin Watson [[email protected]] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
