tag 712185 -moreinfo thanks On 14 June 2013 07:49, Ansgar Burchardt <ans...@debian.org> wrote: > Dmitrijs Ledkovs <x...@debian.org> writes: >> --- at-3.1.13.orig/rc >> +++ at-3.1.13/rc >> @@ -21,6 +21,17 @@ >> >> . /lib/lsb/init-functions >> >> +if init_is_upstart; then >> + case "$1" in >> + stop) >> + exit 0 >> + ;; >> + *) >> + exit 1 >> + ;; >> + esac >> +fi >> + >> case "$1" in >> start) >> log_daemon_msg "Starting deferred execution scheduler" "atd" > > I don't want to have a Debian-specific diff. Why is this required? Can't > upstart detect by itself that it doesn't have to use this init script? >
Upstart/update-rc.d/service do not require above to determine whether or not the init script should be used. Above is only a safe-guard against directly executing the init.d script by the system administrator or any third party tools. The "service" command should be used instead, which correctly can detect whether to invoke upstart or sysv init.d scripts. Please also see a thread, I started on debian-devel [1], about this issue. This safe guard can be alternatively implemented without modifying init scripts. But that also has it's down-sides. That thread also includes links to the debian policy bug where it was introduced to include user-guards in the init.d scripts. >From my point of view, including/installing upstart job with dh_installinit is the only piece that is required to integrate your package correctly with both upstart & sysv init at the same time. Leaving out modifications to the init.d script. [1] http://lists.debian.org/debian-devel/2013/06/msg00658.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
