[00:34] Hi, I want to create an upstart job, which starts a daemon. The application can be run so that it stays in the foreground, or it can be run so it goes to the background. Which mode should I use? I would prefer the first, so I don't have to specify "expect fork". Any reason why the second is better? [00:35] Where can I find example upstart config files (by using a web browser)? [00:40] A daemon is typically ready at the point it daemonizes, but not yet at the point it’s executed. Daemonizing is one of the ways to tell Upstart “i’m started”. With the current release of Upstart, one needs to be very careful with the expect stanza to avoid confusing Upstart: the program must fork in precisely the expected way. For job definitions, look at /etc/init. === ion_ is now known as ion [01:18] http://upstart.ubuntu.com/faq.html#native-jobs-where points to https://code.launchpad.net/~keybuk/upstart/replacement-initscripts but this page does not exist, can someone fix the documentation? === apachelogger is now known as fdsafdsafdsafdsa === fdsafdsafdsafdsa is now known as darthlulu === darthlulu is now known as apachelogger === JanC_ is now known as JanC