Upstart job's process getting killall-ed on reboot

[Scott James Remnant]

On Mon, Apr 4, 2011 at 10:53 AM, Clint Byrum <clint at ubuntu.com> wrote:

> Excerpts from James Hunt's message of Mon Apr 04 03:31:34 -0700 2011:
> > Well, I think the main issue is really with the sysvinit package and the
> > openvt job configuration file. It does beg the question though how a
> > "pure" Upstart installation (in other words a system with no SysV legacy
> > support) would/should handle shutdown cleanly. One option of course
> > would be to create a shutdown.conf that stopped all jobs (ensuring it
> > stopped itself last of course :-)
>
> I think a pure upstart system still would have an event like 'runlevel 6'
> where a user wants a reboot, and 'runlevel 0' where the user wants the box
> to halt. The only difference is, I think they'd call these 'reboot' and
> 'halt', and there'd be a shutdown-process job that defined the order.
> Things that want to insert themselves in this would simply start on
> starting/stopped any of these tasks.
>
> "reboot", "poweroff" and "halt"

Though I was thinking that they might instead be:

  shutdown FOR=reboot|poweroff|halt

since the reason you're shutting down is pretty much irrelevant for the most
part.

I also remember Johan suggesting that we replace "startup" with a "system"
state, in which case it'd be more like:

  system pre-stop SHUTDOWN=reboot|poweroff|halt
  <processes killed and filesystems unmounted by init here>
  system post-stop SHUTDOWN=reboot|poweroff|halt
  <init calls reboot()>

That might make some amount of sense instead.

Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/upstart-devel/attachments/20110404/ce4df2c4/attachment.html>