Re:Spotify position in support of systemd in the default ini...
by mixmastamyk on Saturday January 18, 2014 @01:01AM
(#7080286)
Works for me. What is the problem?
[ Parent
| on HN ]
Re:Spotify position in support of systemd in the default ini...
by STRML on Saturday January 18, 2014 @10:48PM
(#7083301)
For example, there is a long-standing bug [1] where an improperly configured job using "expect fork" can cause upstart to become completely confused and unfixable without a reboot (or a really hacky ruby script [2]).
As the comments discuss, it's not really always clear all the time when to use "expect fork" vs "expect daemon" and the rules change with a `script` block. So this hits people all the time, including me.
It's these kinds of bugs in upstart that bite people all the time. I could go on about its obtuse configuration but I can declare unequivocally that upstart configurations are my least favorite part of system administration, bar none. `Start-stop-daemon` reduces some of the pain but is also difficult to debug.
1. https://bugs.launchpad.net/upstart/+bug/406397 2. https://github.com/ion1/workaround-upstart-snafu/