Upstart 0.9.2 PPA for testing

[James Hunt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi All,

As a precursor to pushing this update out to Natty next week, I've
updated my upstart-testing PPA with Upstart 0.9.2:

	ppa:jamesodhunt/upstart-testing

Code is here:

	lp:~jamesodhunt/ubuntu/natty/upstart/proposed-stage2

The major changes (which will be added to
(https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverview) are...


==== Basic Job/Event Visualisation ====

Upstart provides a new Python script `initctl2dot` which converts the
output of the new `initctl show-config` command to
[[http://www.graphviz.org/|GraphViz]] format. By default, all job
configuration files are considered and the links between jobs and events
are displayed graphically. Additionally, it is possible to list a set of
jobs to graph. Run "{{{initctl2dot --help}}}" or "{{{man initctl2dot}}}"
for full options.

==== New Initctl Commands ====

Two new `initctl` commands have been added:

 1. `show-config`
 1. `check-config`

The `show-config` command displays core job configuration details,
namely the `start on`, `stop on` and `emits` stanza information. This is
useful since it allows users to see how Upstart has parsed the job
configuration files. Additionally, the `show-config` command accepts an
optional `--enumerate` option which makes it easy to see which elements
of complex conditions are jobs, which are events and which are
environment details. This option forms the basis of the Visualisation
feature above.

The `check-config` command is useful for System Adminstrators and
tooling to ensure that all jobs are theoretically startable/stoppable.
For example, if a job configuration file specified the following complex
condition:

{{{
  start on (A and (B or (starting C or (starting D or starting E))))
}}}

The `check-config` command would flag an error if for example none of
the jobs 'C', 'D' or 'E' were available since that would indicate
the job in question could never be automatically started (since the
start on condition could never be true). Similar checks are performed on
events, so if jobs 'C', 'D' and 'E' are available but events 'A' and 'B'
are not advertised as being emitted by any job, 'check-config' will
generate an error. If no errors are detected, `check-config` displays no
output and returns zero. If errors are detected for a job, each
condition that is unsatisfiable is displayed with a message.

==== Miscellaneous ====

 * A new manual page, `upstart-events (8)` summarising well-known
Upstart events.
 * An updated [[http://www.vim/org|Vim]] syntax file has been included.
 * A Bash completion script has been included for `initctl`.
 * A new script `init-checkconf` has been provided which allows a user
to check an individual job configuration file to ensure it is
syntactically correct before installing it in "`/etc/init/`". Run
"{{{init-checkconf -h}}}" or "{{{man init-checkconf}}}" for full options.
 * The [[http://www.vim/org|Vim]] package "{{{vim-runtime}}}" now
includes syntax support for upstart job configuration files.


- -- 
Cheers,

James.
- --
James Hunt
____________________________________
Ubuntu Foundations Team, Canonical.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk16EFIACgkQYBWEaHcQG9eYSwCfXSGgqDlX8F6mN8UONzDHlyVZ
LAYAnRivuH8Lj1Q1uuqZNn6u7Csr9RtN
=8LZc
-----END PGP SIGNATURE-----