From: James Hunt <james.hunt@ubuntu.com>
To: "upstart-devel >> \"upstart-devel >> Upstart Devel List\""
<upstart-devel@lists.ubuntu.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Upstart 1.8 released
Date: Fri, 22 Mar 2013 14:58:50 +0000 [thread overview]
Message-ID: <514C71AA.7090900@ubuntu.com> (raw)
Hot on the heels of v1.7, this new release adds two interesting new features:
- upstart-file-bridge: a new bridge that allows jobs to react to file
events.
Examples:
# Event emitted when file is created, modified or deleted
start on file FILE=/run/app.pid
# Event emitted when file is created (only)
start on file FILE=/run/app.pid EVENT=created
# Event emitted when files within a directory are created,
# modified or deleted.
start on file FILE=/var/log/
# Event emitted when files that match a glob pattern are
# created in the indicated directory.
start on file FILE=/var/crash/*.crash EVENT=created
See upstart-file-bridge(8) and file-event(7) for further details.
- upstart-monitor: a very simple tool (*) that can run in either CLI or
GUI mode either connected to PID 1 or a Session Init (as root or
non-root) that allows users and admins to see event flows.
See upstart-monitor(8) for further details (and [1] for obligatory screenshot).
Thanks to all involved!
Download Upstart 1.8 from launchpad: https://launchpad.net/upstart
Kind regards,
James.
(*) - If you are interested in contributing to Upstart, we'd love to hear from
you. Now is a great time to get involved, since with the advent of the
upstart-monitor the fun expands to include GUI hackers too ;-)
[1] -
http://ifdeflinux.blogspot.co.uk/2013/03/a-basic-upstart-events-gui-and-cli-tool.html
--
James Hunt
____________________________________
#upstart on freenode
http://upstart.ubuntu.com/cookbook
https://lists.ubuntu.com/mailman/listinfo/upstart-devel
reply other threads:[~2013-03-22 14:58 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=514C71AA.7090900@ubuntu.com \
--to=james.hunt@ubuntu.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 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.