[18:20] hey guys. i am reading the "getting started" page. this makes no sense, syntactically speaking:You can change the settings for where a job's output goes, and where its input comes from, with the console stanza. This should be one of output (input and output from /dev/console), owner (as output and Control-C also sent the process) [18:20] as output and control-c also sent the process? [18:21] project2501b: if you don't have any special requirements, just don't specify the console stanza which will discard any output from the job. [18:22] project2501b: there's a new feature that will be available soon that adds 'console log' such that any output from a job can be logged to a file. [18:22] project2501b: You may want to see the cookbook rather than the (dated) "Getting Started" page: http://upstart.ubuntu.com/cookbook/ [18:23] jhunt: cool beans, dude [18:23] jhunt: i am using upstart in a 20k core bioinformatics cluster. [18:23] great way to test if the node is within required parameters :D [18:23] jhunt: but i am talking about the wording in the page [18:24] project2501b: now *that* sounds like cool beans to me! :) [18:24] it might be my english, but to me that sentence makes no sense [18:24] "also sent the process"? [18:24] you mean "are also sent to the process"? [18:24] project2501b: try "man 5 init" and searching for "console". init(5) is "the bible" for Upstart. [18:25] jhunt: with a raid 6+0 over ssds, i managed to reduce the boot up time of the entire cluster from 5 hours down to 40 minutes :p [18:26] jhunt: i get it about init. i am saying that the wording on the page, might be erroneous [18:26] jhunt: and i am asking, i guess, for confirmation, if you think the wording is also wrong or not. [18:27] http://upstart.ubuntu.com/getting-started.html [18:29] project2501b: fixed. [18:30] ok! :D [18:30] beer, bacon, linux and cute german women around me. what else could i ask? [18:30] thanks man :) [18:31] project2501b: np. are you running Ubuntu on this cluster? [18:31] no. Debian [18:31] so, you're probably using a pretty old version of upstart. We're trying to rectify that atm... [18:32] i do not agree with the Ubuntu philosophy nor do i agree with the philosophy of its users. [18:32] neither do i think that canonical is doing a good job [18:32] jhunt: no prob, i am running wheezy [18:33] but upstart is the right way out of the monolithic age, for sure. [18:33] with so many cores, why not put them to use? [18:34] jhunt: if i make another suggestion, you are saying at the end of the page "Events can taken arguments (passed on the emit command-line) in the form of environment variables." [18:34] project2501b: of course. if you're allowed to (?), maybe you could blog about that setup? [18:35] you might want to put an example there to clarify it, and leave everything else for the full guide. [18:35] other than that, i think the getting started guide is quite excellent. [18:35] jhunt: love to, not allowed to. [18:35] uni i work for is kinda hush hush for its resources. [18:35] but you may see me in SC11 [18:36] project2501b: the material on upstart.ubuntu.com needs to be folded into the cookbook since this is where we are concentrating our efforts. You can download a pdf of the entire cookbook if you want to read offline. Rest assured we will tidy up that top-level site "real soon now" :) [18:36] project2501b: noted. [18:36] cookbook? do i smell an oreilly cookbook? :D [18:36] That wasn't the original plan, but who knows? [18:37] heh. [18:37] upstart and gnu parallel. let's see if we can make a map reduce function in shell. [18:37] jhunt: thank you :) [18:37] project2501b: np - any time.