| Keybuk | my life was so much easier when I worked on computers that would boot any USB key :p | 00:17 |
|---|---|---|
| === hallyn is now known as hallyn_afk | ||
| elik | Is it possible that upstart would limit the creation of child processes? | 04:27 |
| ion | elik: Use ulimit. | 14:00 |
| === hallyn_afk is now known as hallyn | ||
| === marrusl is now known as marrusl_afk | ||
| === hallyn is now known as hallyn_afk | ||
| === hallyn_afk is now known as hallyn | ||
| iaindalton | in my pre-start script, I have "echo foo starting >/somefile; /path/to/foo; echo foo done >>/somefile", but /somefile only has "foo starting", even though the script's status is stop/waiting, and pgrep confirms foo isn't running. What's happening? | 21:18 |
| JanC | iaindalton: probably foo stopped with an error? | 21:19 |
| iaindalton | JanC: why wouldn't the next line execute? I'm not using && | 21:20 |
| JanC | upstart runs scripts with "set -e" (basically: stop the script when a command returns with an exit status value > 0) | 21:22 |
| iaindalton | ah; is there a way to get at the exit status? The reason I put those echos in was to debug why it was exiting early, since running /path/to/foo from the terminal after the system boots works fine | 21:23 |
| iaindalton | and where does foo's output go when started by upstart? | 21:23 |
| iaindalton | I'm searching the docs for this info too | 21:24 |
| Keybuk | it goes to /dev/null | 21:25 |
| iaindalton | ah, output goes to /dev/null | 21:25 |
| Keybuk | the exit status of the pre-start script should be in your syslog | 21:25 |
| iaindalton | what if I instead have exec /path/to/foo after the pre-start script? Still in /var/log/syslog? And what do I grep, the name of the script? Because I didn't get anything. | 21:27 |
| mbiebl | iaindalton: have you tried "console output" ? | 21:32 |
| Keybuk | iaindalton: initctl log-priority info | 21:34 |
| iaindalton | Yeah, but everything scrolled by too fast for me to tell if it worked. I assume it's in a log file though, just gotta find it. | 21:34 |
| iaindalton | Keybuk: what's that? Does nothing for me | 21:34 |
| Keybuk | then your syslog must be configured to drop messages from init | 21:36 |
| iaindalton | Yeah, looking into that now :-) | 21:39 |
| iaindalton | Wait, was I supposed to run initctl log-priority info at the terminal, or stick it somewhere in my startup script? | 21:40 |
| Keybuk | at the terminal | 21:41 |
| iaindalton | And what's supposed to happen? | 21:41 |
| Keybuk | upstart sends more to syslog | 21:44 |
| iaindalton | ah, but my script has already quit by the time I log in, so I'd need to run it again, right? | 21:44 |
| iaindalton | except when I run it after logging in, it works fine | 21:44 |
| iaindalton | well, I messed with syslog, and now I have the message. Thanks for the help | 21:47 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!