❦ 21 janvier 2014 14:00 CET, Lucas Nussbaum <lucas@debian.org> :
> At this point of the discussion, stating that "one aspect didn't get the
> attention it should get." sounds a lot like "I didn't bother to search the
> archives". :-)
The fact that Upstart's proponents didn't outline important bugs in
Upstart may also been seen as "one aspect didn't get the attention it
should get". In the different final positions of the TC in favor of
Upstart, we don't see mentions of those important bugs:
https://bugs.launchpad.net/upstart/+bug/516713
https://bugs.launchpad.net/upstart/+bug/447654
https://bugs.launchpad.net/upstart/+bug/406397
As Matthias, I wanted to point those out since a long time: how can we
choose Upstart when there are critical bugs that remain unfixed for
years?
I particularly hate the last one that bite me several times: you make
one mistake ("expect fork" instead of "expect daemon") and you need to
either reboot your system or know this script:
https://github.com/ion1/workaround-upstart-snafu
Colin proposed to never use "expect fork" and "expect daemon", but they
exist and our users will write Upstart jobs to start their scripts,
daemons, workers, etc.
--
/* Am I fucking pedantic or what? */
2.2.16 /usr/src/linux/drivers/scsi/qlogicpti.h
Attachment:
signature.asc
Description: PGP signature