[00:03] I am wondering if the following is a bug or a feature: [00:03] when I start two instances, each one with a different value (via a key) of instance variable "A" [00:04] ANd then stop one using a specific KEY and it stops both instances. [00:04] I would have expected only the one with the specified key that matches a specific instance would be stopped: [00:04] See gist http://gist.github.com/404349 [00:10] ${ probably evaluates to either the string ‘${’ or the value of the environment variable {, and A} is appended to that string. [00:33] If I get rid of the brackiets (ie $A instead of ${A}) it still acts the same and kills both instances [00:33] (That last message was for ion) [02:27] ANyone know if upstart can do user-defined conf.d style directories ? ie, does it have a "include" statement? I can't find decent docs on its configuration [03:55] shit [03:56] runit cant be configured because runit is not running [03:56] what do i do? [03:56] borked upgrade [03:56] that is the only package i have remaining to configure/upgrade [03:56] and i think it is what is preventing my system from coming up [03:56] i have to init=/bin/bash [03:57] do i try to install sysvinit or something [03:57] and then runit? [07:22] sry about that [19:32] hi everyone. how do I make upstart recognize my script upon placing it in /etc/init ? [19:32] rockhound: if its named something.conf and is free of syntax errors, upstart will pick it up immediately [19:33] sadmac: then it must be syntax errors ;-) [19:33] rockhound: /var/log/messages should have the errors [19:34] sadmac: perfect ... thanks for the hint [19:38] keybuk: http://www.fark.com/cgi/comments.pl?IDLink=5297633&hl=Kim-Kardashian-wants-a-man-who-sees-her-good-qualities-five-lights [19:41] THERE [19:41] ARE [19:41] FOUR [19:41] LIGHTS! [21:58] pid stanza seems to be unkown in 0.6.3 ... any way that I can pass a correct pid file [22:03] hold the answer ... will be back tomorrow ;-)