| hackel | Is there any way to determine the configuration file associated with an upstart job? Preferably via dbus? | 06:17 |
|---|---|---|
| JanC | hackel: file & job have the same name? | 10:48 |
| hackel | JanC, is that always a certainty or merely a coincidence? | 10:57 |
| hackel | That's what I wound up doing, it just felt like a bit of a hack. | 10:57 |
| JanC | it's explained in the first section of the manual... | 10:58 |
| hackel | Okay, thanks. | 11:00 |
| Omahn | I have a *really* basic upstart script that hangs when I try to stop it and I've no idea why. If I manually send a TERM signal to the exec'd process then the process stops fine so I'm at a loss why upstart is seemingly hanging. Any clues? Script is here: http://paste.ubuntu.com/447777/ | 14:36 |
| plautrba | Omahn: "expect fork" doesn't work with "script" | 14:40 |
| Omahn | plautrba: Ok, is the solution moving my domainname line to a pre-start section and then just using an exec rather than script section? | 14:42 |
| plautrba | Omahn: i think it is | 14:43 |
| Omahn | plautrba: I'll give that a try then, thanks. | 14:43 |
| Omahn | In addition to the above change, a switch to 'fork daemon' appears to have resolved my issue. | 14:49 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!