Easiest solution would be setting 'respawn limit' to more tolerant value.

(In reply to comment #2)
> Easiest solution would be setting 'respawn limit' to more tolerant value.

What we need is 'forever'.  Setting it to a finite value is not a solution.

There is a patch in the launchpad bug referenced.

We are probably not planning to update upstart in next release, but you can also create second job which will be launched when the main job fails and stops respawning, and watch for network to go online again.


::::::::::::::
job.conf
::::::::::::::
start on startup or mycheck FILE=exists
script
	while [ -e /tmp/aaa ]; do sleep 1; done
end script
respawn

::::::::::::::
test.conf
::::::::::::::
start on stopped job
script
	echo "File disappeared"
	while [ ! -e /tmp/aaa ]; do sleep 10; done
	echo "File appeared"
	initctl emit mycheck FILE=exists
end script

I want "respawn forever" option too.

Say, an unprivileged user is operating on console login. He used nested shells
(bash -> bash -> bash), and he finished his job. He pressed Ctrl-D for three
seconds so that all the nested shells are exited and he can completely log out
and the login prompt will appear. What will he get?

He gets a login prompt which no longer responds (because the mingetty process
is no longer respawned, like /var/log/messages says "init: tty (/dev/ttyX)
respawning too fast, stopped"). He can never login again from that tty. ;-(

(If he is malicious, he can kill all console ttys so that nobody can login from
console.)

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

The original patch was never accepted upstream.