Influencing upstart from within a job

[Scott James Remnant]

How each distribution implements their shutdown process is up to then, if
"shutdown now" doesn't work within your boot sequence, you should contact
the distribution to find out what method does work.

On Thu, Feb 17, 2011 at 12:18 PM, Jon Stanley <jonstanley at gmail.com> wrote:

> Sorry that I couldn't find a users list to deal with upstart (but then
> again, most users probably don't care too much about the init
> system... :D). Anyhow, I'm trying (and I've talked to a few people in
> person about this) to influence the behavior of upstart from within an
> upstart job. This is on RHEL6, which uses 0.6.5 in mostly
> compatibility mode.
>
> To put this in more concrete terms, I have a job that gets run one
> time, when a server is first installed. This is done by a very simple
> upstart job, and the complexity is in the scripts executed by the job
> (basically, I'm using the SysV compatibility wrappers to start a
> "runlevel 9". This job is executed at "start on starting rc". When
> this job is complete, I need the system to reboot, not continue on
> past this job. The job takes care of removing itself on success.
>
> Trying to use /sbin/init 6, for example, within the job fails to do
> anything. The only way that I could find to effect a reboot is to use
> something like /sbin/reboot -f, but that has the unfortunate side
> effect of an unclean reboot.
>
> Am I missing something here, or is there really no good way to do this?
>
> --
> upstart-devel mailing list
> upstart-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/upstart-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/upstart-devel/attachments/20110217/1cd09401/attachment.html>