Comment 6 for bug 252997

Same problem, we have processes depending on some other processes on the same or on remote servers. We have N servers controlling/controlled by M servers which are controlled by telco hardware. If one out of M servers goes down (hardware or some processes due to administrative task or telco alarm or anything else) we have to manually restart some processes on M servers.

We ported some daemons from one server/distrribution using old init system to new server using upstart (0.3.x), assuming plain old unix init behaviour when respawning daemons. We had to workaround about upstart respawn behaviour using scripting in order to emulate old init behaviour... quite dirty and not responsive....

Generally speaking, we encountered this 'bug', but shouldn't upstart provide all old init behaviour regarding managed processes (may be this one is the one missing, don't know) ?