From: James Hunt <james.hunt@ubuntu.com>
To: linux-kernel@vger.kernel.org
Subject: Upstart 1.3 released (yesterday :)
Date: Wed, 15 Jun 2011 17:27:21 +0100 [thread overview]
Message-ID: <4DF8DD69.3010406@ubuntu.com> (raw)
A plethora or new features and updates, including all those from Ubuntu Natty.
* New upstart-socket-bridge application which allows jobs to be
started when an incoming client socket connection is initiated
(requires a suitably modified server daemon since jobs only
need call accept(2) before reading from the socket).
* User session support allowing non-privileged users to
manipulate their own jobs (not available within a chroot
environment).
* Chroot support allowing jobs to be controlled within chroot
environments.
* Updated bash completion script.
* Updated vim syntax script.
* init-checkconf script used to check syntax of Job
Configuration Files (including script sections).
* initctl2dot script to convert initctl(8) output to GraphViz
dot(1) format for analysing relationships between jobs and
events.
* New "check-config" initctl command to check for jobs whose
* "start on" and "stop on" events cannot be satisfied.
* New "show-config" initctl command to display "start on", "stop
on" and emits" information in parseable format.
* New initctl command-line option: "--session" for D-Bus
session connection.
* New init command line options (mostly for testing):
- "--session" for D-Bus session bus.
- "--confdir <dir>".
- "--startup-event <event>".
- "--no-startup-event".
* New "kill signal" stanza to allow override of SIGTERM when
stopping jobs.
* Add support for the oom_score_adj procfs API.
* Improved POSIX compliance when running shell scripts.
The tarball can be found here:
https://launchpad.net/upstart/1.x/1.3
For more information on upstart:
http://upstart.at/
http://upstart.ubuntu.com/
Regards,
James Hunt
reply other threads:[~2011-06-15 16:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF8DD69.3010406@ubuntu.com \
--to=james.hunt@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.