From: James Hunt <james.hunt@canonical.com>
To: "upstart-devel >> Upstart Devel List"
<upstart-devel@lists.ubuntu.com>,
linux-kernel@vger.kernel.org
Subject: Upstart 1.5 released
Date: Thu, 22 Mar 2012 11:39:18 +0000 [thread overview]
Message-ID: <4F6B0F66.40505@canonical.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Summary of changes:
* Lots of "console log" improvements (and new tests).
* New 'early logging' facility which allows jobs that end before the
log disk is writeable to have their output peristed to disk when the disk
later becomes writeable.
* Upstart is now able to detect jobs which leak file
descriptors: a message is generated when run with debug enabled
('--debug' / "initctl log-priority debug").
* New "usage" stanza which allows instance jobs to display a usage
message explaining how job should be started. The usage is displayed
when the user has not specified the correct variables to allow the job
to be started, or when the user queries the usage using
"initctl usage <job>".
Download it from launchpad: https://launchpad.net/upstart
Kind regards,
James
- --
James Hunt
____________________________________
http://upstart.ubuntu.com/cookbook
http://upstart.ubuntu.com/cookbook/upstart_cookbook.pdf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPaw9lAAoJEJ1Q4UTmNXMn/y4QAJUkxQ88FlN4Hsu3zKOhSJWs
0VXeSLRlmNhWNdK52A1iZO/BshjaEGrpWICTjNmlY7OWJvey2JxNgF24O9kAqAIK
jxXsn1H3QWAceot8t0KxHEeFqToGeJaPzAh+SXMnlHItp0S8PAAsE2zmrlw06buI
yBvDOk5BG4SGeBj4o2fiDC1zGd3d8XWH3cJhi7vpqUniiXAYJFw5HGLUJYCxFmff
L2VFiAX0gn0KNAFVrbQDpYBRq4ZegUc4H0FQUjWNpOWU6v4jZ0rZmWD/7ETmgpkk
fDRpq65La8HrP+LlY4VM74POkOk18QQJGiM1jpXWv0fq6z5tRUGMjnpfUigOuGiw
7Ws749NpKApjiUh2azON89tS0Vb3IQdW0zGdjsL9FOQ+B6u03PbmSwMa/JkMSYh0
+OkOhK17Lx/6ooHnW6Sr83Q/5WhEMsBacLOSi0nCJJlrJLS9K/vINDCR6iQqsl1B
ixe6FsdCxdQSE7aCt2euIi5AKTWOoMzEi8gu6me0mF7XTT7ezpxbcc6n7vAE2X7C
iOluM13DgeZH9Zmf9/q8v39HQ9vi5FT+DC0hmM/UQQB/XNfiLJtpLzysOZV0sfq/
6jN1B/UdgAjHbzwmkeUY/jWGwDvamEGDw38xb/As+g7gt+TxuICOfqBfOE142t19
MDDAq/1NcMWYzJSwbE27
=6nMB
-----END PGP SIGNATURE-----
reply other threads:[~2012-03-22 11:39 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=4F6B0F66.40505@canonical.com \
--to=james.hunt@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=upstart-devel@lists.ubuntu.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox