[17:45] where does upstart hold its state? i'm running into issues where one a job isn't detected as starting properly any start/stop hangs [17:45] unless I change my job name [17:45] (0.6.5) [17:46] i think my process is forking too many times as the pid upstart thinks it is/was didn't sitcka round [17:50] wish there were some effort put into getting some updated documentation [17:50] esp re: how to debug your scripts [18:12] Yeah, that’s a known problem. Better not use ‘expect’ unless you’re completely sure of the forking behavior of your main program. A future release of Upstart will come with a better implementation of following forks. [18:12] The state’s in memory. === Stevee_ is now known as Stevee [19:04] Hello [19:09] i like to know how to change the key combinations Ctrl Alt DEL [19:10] nobody can not repondre me [19:14] Guest33795: this isn't the correct channel for that question [19:14] ion: so for now, if it double-forks, I can't use upstart to manage it? [19:14] correct? [19:15] ‘expect daemon’ follows a main process that forks twice. [19:29] hrm [19:30] in my case the stop will then hang when the pid is not actually a running process [19:30] then any7 subsequent start/stop hangs [19:31] Yeah, the current functionality gets confused very easily if the main process behaves differently than what the ‘expect’ stanza says. === transitlogger is now known as apachelogger