Comments on: Upstart 0.5: Events http://www.netsplit.com/2008/04/27/upstart-05-events/ Just another WordPress weblog Sat, 05 Jul 2008 08:48:35 +0000 http://wordpress.org/?v=2.5.1 By: giko http://www.netsplit.com/2008/04/27/upstart-05-events/#comment-861 giko Wed, 25 Jun 2008 12:43:09 +0000 http://www.netsplit.com/?p=147#comment-861 Hi, I want to trigger a script when a device (.f.ex. usb dongle, usb bluetooth etc) i removed. I read that upstart can be triggert on these events (emitet by the kernel, hal or dbus) but i do not know the name "?" of the event to trigger on. Could you help me out there? /giko Hi,

I want to trigger a script when a device (.f.ex. usb dongle, usb bluetooth etc) i removed. I read that upstart can be triggert on these events (emitet by the kernel, hal or dbus) but i do not know the name “?” of the event to trigger on. Could you help me out there? /giko

]]> By: Frymaster http://www.netsplit.com/2008/04/27/upstart-05-events/#comment-826 Frymaster Mon, 28 Apr 2008 13:05:59 +0000 http://www.netsplit.com/?p=147#comment-826 The only annoying this about upstart as-is (I can't comment on upstart 5 which is upstart as-it-will-be) is I have literally no clue which of these keywords are in the version of upstart in my distro (which is version 0.3.8), or indeed which other keywords NOT described are there, or what they might do. While there is a very good getting started guide on this webite, it is pretty much the only documentation that exists, and it _IS_ only useful for getting started, not finished. "man event.d" does nothing, "man upstart" does nothing, "man init" leads via the "see also" section to initctl, which is interesting but also doesn't help in writing the things. The example jobs are of the very simple kind and are similarly unhelpful. (The existance of a pre-stop script and a post-start was inferred from the existing examples, but aren't explicitly mentioned anywhere) Just from what has been casually dropped in here and on I know there's a "task" keyword, but have no idea what that means. There are tantalising hints to some kind of logging facility (which is what I'm tearing my hair out over at the moment) but I have no idea how to invoke it, or even to redirect output somewhere sensible, other than redirecting at the end of the line calling the program (which then triggers that app's very annoying let's-buffer-1-screen-at-a-time mode). If I put the app at the beginning of a pipe, stopping the job kills the shell that's calling the program without killing the program itself and I have no idea how to fix it. I have no clue what events might fire on my system, or what might decide to fire them, and have no systematic way of finding out. I have no idea how to carry state information forward from pre-start scripts to the start script itself, other than creating tons of temp files. In short, I need documentation :( The only annoying this about upstart as-is (I can’t comment on upstart 5 which is upstart as-it-will-be) is I have literally no clue which of these keywords are in the version of upstart in my distro (which is version 0.3.8), or indeed which other keywords NOT described are there, or what they might do.

While there is a very good getting started guide on this webite, it is pretty much the only documentation that exists, and it _IS_ only useful for getting started, not finished. “man event.d” does nothing, “man upstart” does nothing, “man init” leads via the “see also” section to initctl, which is interesting but also doesn’t help in writing the things. The example jobs are of the very simple kind and are similarly unhelpful. (The existance of a pre-stop script and a post-start was inferred from the existing examples, but aren’t explicitly mentioned anywhere)

Just from what has been casually dropped in here and on I know there’s a “task” keyword, but have no idea what that means. There are tantalising hints to some kind of logging facility (which is what I’m tearing my hair out over at the moment) but I have no idea how to invoke it, or even to redirect output somewhere sensible, other than redirecting at the end of the line calling the program (which then triggers that app’s very annoying let’s-buffer-1-screen-at-a-time mode). If I put the app at the beginning of a pipe, stopping the job kills the shell that’s calling the program without killing the program itself and I have no idea how to fix it. I have no clue what events might fire on my system, or what might decide to fire them, and have no systematic way of finding out. I have no idea how to carry state information forward from pre-start scripts to the start script itself, other than creating tons of temp files.

In short, I need documentation :(

]]>