On 3 May 2014 03:04, Steve Langasek <vor...@debian.org> wrote: > Hi Cameron, > > On Fri, May 02, 2014 at 06:35:30PM -0700, Cameron Norman wrote: >> Hey Steve, > >> Is there anything wrong with the script attached by Dimitri ( to >> implement the no-op init script functionality mandated by policy)? If >> not, would you like me to create a deb diff to add the script to the >> appropriate directory? > > Actually, this bug report had fallen off my radar. I had been expecting > Dimitri to implement this in Ubuntu, and that I would cherry-pick it back > into Debian. Dimitri, is this patch current, and do you want it included > as-is? I seem to recall some discussion about making the init scripts > pass-through to upstart rather than making them silently fail; did that > discussion reach a conclusion? > > Assuming we're ok with the behavior provided by this patch, the only thing I > would change is to check for the existence of the upstart job first, before > checking whether init_is_upstart, since it's the cheaper operation. > > Also, why the check for /etc/init/foo.conf as a symlink? Is that because > upstart doesn't follow symlinks for .conf?
Indeed i now wish to intercept commands and pass them through to upstart direct, similar to how service command does it. Check for symlink is indeed because upstart doesn't follow symlinks, however zero exit status from "initctl --system status job 1>/dev/null 2>/dev/null" is a more authoritative answer whether a job exists from upstart's point of view. -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
