[00:02] <Tv> actually to correct myself, IIRC runsv doesn't put a process in between, it just keeps the read side of the pipe alive in the parent, and starts a new log consumer if old one exits
[00:03] <Tv> which would be doable in upstart, i guess
[00:14] <mbiebl> Keybuk: hi
[00:14] <Keybuk> hey
[00:15] <mbiebl> About 0.5 and dbus:
[00:15] <mbiebl> If want to schedule reconnect attempts within upstart, where should I best do that
[00:16] <mbiebl> so it also works for systems, where dbus daemon is started *after* upstart