| traviscline | 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 |
|---|---|---|
| traviscline | unless I change my job name | 17:45 |
| traviscline | (0.6.5) | 17:45 |
| traviscline | i think my process is forking too many times as the pid upstart thinks it is/was didn't sitcka round | 17:46 |
| traviscline | wish there were some effort put into getting some updated documentation | 17:50 |
| traviscline | esp re: how to debug your scripts | 17:50 |
| ion | 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 |
| ion | The state’s in memory. | 18:12 |
| === Stevee_ is now known as Stevee | ||
| Guest33795 | Hello | 19:04 |
| Guest33795 | i like to know how to change the key combinations Ctrl Alt DEL | 19:09 |
| Guest33795 | nobody can not repondre me | 19:10 |
| traviscline | Guest33795: this isn't the correct channel for that question | 19:14 |
| traviscline | ion: so for now, if it double-forks, I can't use upstart to manage it? | 19:14 |
| traviscline | correct? | 19:14 |
| ion | ‘expect daemon’ follows a main process that forks twice. | 19:15 |
| traviscline | hrm | 19:29 |
| traviscline | in my case the stop will then hang when the pid is not actually a running process | 19:30 |
| traviscline | then any7 subsequent start/stop hangs | 19:30 |
| ion | Yeah, the current functionality gets confused very easily if the main process behaves differently than what the ‘expect’ stanza says. | 19:31 |
| === transitlogger is now known as apachelogger | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!