Code review comment for lp:~jamesodhunt/upstart/bug-1083723-reprise

For now, it seems like it's the only way to workaround that problem.
Obviously this means that telinit won't know whether the restart was successful or not.

I'm currently finishing the tests of my dbus-events branch which adds a new Restarted event emitted right after upstart did a successful re-exec.
In the future, we'll be able to have telinit listen on the system bus (if present) and catch that Restarted signal to confirm that upstart re-exec properly.