[22:51] <davidstrauss> Am I correct to interpret the docs as saying the minimum for an upstart script is simply an "exec" line?
[22:55] <ion> That’s optional, too.
[22:55] <ion> The minimum job definition is an empty file.
[22:56] <ion> There are a number of important use cases where a job doesn’t have a main process.
[22:56] <davidstrauss> ion, dependency routing?
[22:57] <ion> For instance, something that changes the system state in some way in the pre-start script and changes it back in the post-stop script, such as /etc/init/apport.conf
[22:59] <davidstrauss> ion, One more question. What does this mean by "optional arguments to pass to it"? "exec gives the path to a binary on the filesystem and optional arguments to pass to it"
[22:59] <ion> % echo foo
[22:59] <ion> foo
[23:00] <davidstrauss> ion, Should that instead say "and, optionally, arguments to pass to it"
[23:00] <ion> “foo” here is an argument. From Upstart’s point of view, all program arguments are optional.
[23:01] <davidstrauss> ion, Sure. I'm just trying to figure out if the doc is trying to say that (1) upstart manages optional arguments to an executable in some configurable way or (2) that upstart allows you to pass in arguments on the exec line
[23:02] <ion> 2
[23:02] <davidstrauss> ion, OK. Where can I file a request to revise the docs?
[23:02] <ion> As a bug report on Launchpad, or as a merge request on Launchpad.
[23:05] <davidstrauss> ion, the getting started guide doesn't appear in the source branch; am i missing something?
[23:05] <ion> Ah, i was thinking you were reading init(5) or something.
[23:06] <davidstrauss> ion, I'm reading this: http://upstart.ubuntu.com/getting-started.html
[23:07] <ion> I guess one could still report a bug against Upstart, since the web page is part of the project, kind of. Or bug Keybuk on IRC. :-)
[23:12] <davidstrauss> ion, https://bugs.launchpad.net/upstart/+bug/689939