[05:20] <DanaG> Say, I'm having trouble writing an upstart rule/job/scriot (whatever you call it)... if I try to start it, the 'start' command hangs forever, and nothing happens.  There isn't even a logged failure in syslog, and the log with the upstart job's name doesn't exist.  I've stripped it down to a minimal test case, and even this fails:  http://pastebin.com/D8wEy8fW
[05:40] <jY> sounds like a fork problem
[05:42] <DanaG> hmm, I'll try adding 'expect fork', even though a simple '/usr/bin/env' (print environment variables) ought not to fork itself...
[05:43] <DanaG> Last thing I see with initctl loglevel at debug: "asset-upnp goal changed from stop to start".... then nothing.
[05:43] <DanaG> Okay, that didn't change anything.
[05:44] <DanaG> hmm, is it possible for upstart itself to get stuck in a screwed-up state where it refuses to do things?  I can stop and start lightdm just fine, but not my own service.
[06:20] <DanaG> gah, for now, I'm giving up, and starting the darn thing in rc.local.
=== Md_ is now known as Md