Let's say I have a job that gets stopped in a couple of ways: stop on stopped foo stop on stopped bar
I'd like to know which triggered me. The environment variable UPSTART_EVENT comes close, but only holds "stopped" (or in other cases, "runlevel") rather than "stopped foo" (or "runlevel 0"). Is this a bug or a feature? If the latter, what's the rationale? Would I be screwing myself if I modified the behavior? Would you take the patch? BTW, sshd's been crashing pretty regularly on my up-to-date Gutsy system. If sshd were launched via an upstart jobfile and respawned I would never notice. That gonna happen someday? :-) Thanks, --Eric -- ****************************************************************************** * From the desktop of: Eric House, [EMAIL PROTECTED] * * Crosswords with Bluetooth on PalmOS now in beta: xwords.sourceforge.net * ****************************************************************************** -- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
