This is not an upstart bug, but a configuration issue: your oident.conf is invalid since:
1) OIDENT_OPTIONS is guaranteed to always be unset since you cannot source options in a pre-start and have them apply to the script stanza since each stanza is run as a separate process. 2) Since OIDENT_OPTIONS is unset and since you have specified 'expect fork', Upstart will follow the PID of the first call to 'logger' in your script stanza. Also, your 'start on' condition might be too permissive since Upstart will attempt to run the job when every net device comes up - is that what you want? Finally, when developing a new job, don't use respawn: make sure the job works correctly before introducing it. Please read the following sections of the Upstart Cookbook: - http://upstart.ubuntu.com/cookbook/#expect - http://upstart.ubuntu.com/cookbook/#using-expect-with-script-sections - http://upstart.ubuntu.com/cookbook/#precepts-for-creating-a-job-configuration-file ** Changed in: upstart (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034776 Title: /sbin/start hung in __GI___poll To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1034776/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
