On Fri, Nov 01, 2013 at 06:49:34PM +0000, Ian Jackson wrote: > Steve Langasek writes ("Bug#727708: Value of reading other's position > statements [was: systemd vs. whatever]"): > > I agree with all of the technical critiques here, I just don't see that this > > relatively minor issue, which can be documented and worked around (and > > ultimately, fixed upstream), is something that should be driving Debian's > > choice of init system.
> One of the reasons that people are worried about replacing the > venerable sysvinit, is that they fear the loss of useful (sometimes, > essential) debugging techniques - of which this is one. But that's an unwarranted fear here. Sysvinit doesn't give you any way to plug in strace without having the exact same kind of service readiness problems - either you can background the strace invocation, and then the process unblocks the flow of execution immediately and the init script may exit before the service is actually working; or you keep strace in the foreground, and the init script as a whole never backgrounds. You have the exact same choices in upstart; people are just less familiar with the interfaces for doing so, and familiarity isn't a good reason to stick with sysvinit indefinitely. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature