[12:25] <mbiebl> Shred01: No, that won't work.
[12:26] <Shred01> is there any reason not to emit events for those old initscripts?  to help interfacing newer ones with older ones?
[12:28] <mbiebl> Do you know, how the current sysv compat layer works?
[12:28] <mbiebl> upstart basically has two jobs: rcS and rc-default (which by default runs rc2).
[12:29] <mbiebl> These two jobs simply run /etc/init.d/rcS and /etc/init.d/rc 2
[12:29] <mbiebl> If you wanted feedback from the old sysv initscripts, you'd either have to modify /etc/init.d/rc or the initscripts directly.
[12:30] <mbiebl> And place corresponding "initctl emit $foo" call in their.
[12:31] <mbiebl> s/their/there/
[12:33] <Shred01> mbiebl: exactly.  i'd of course opt for modifying /etc/init.d/rc.
[12:34] <mbiebl> I guess, the reason why it's not done, is simply that it is not really needed.
[12:35] <mbiebl> Do you have any good use cases?
[12:37] <mbiebl> And modifying /etc/init.d/rc won't address the problem, that you can start/stop services via /etc/init.d/$foo.
[12:39] <mbiebl> So you'd have to modify all initscripts and add "initctl emit $foo $changed_status" everywhere.
[12:39] <mbiebl> A lot of work that would be not worth the effort imho.
[12:40] <Shred01> mbiebl: that is true.  i guess i am just looking from the "orderly starting of services" POV.  the use case is mythtv's existing mythtv-backend initscript.  i want to write an upstart script for myth's frontend (which is not included in the frontend package as an upstart or initscript) but it really can't start until the backend has started.
[12:41] <mbiebl> You would write an upstart job for the backend first.
[12:41] <mbiebl> Replace the initscripts from the bottom up.
[12:42] <Shred01> sure, but then i have a one-of that i need to remember to keep replacing every time i get a mythbackend update.
[12:43] <Shred01> i'm just being impatient i guess and not seeing the point to writing an initscript for mythfrontend vs. writing an upstart script for it.
[12:43] <mbiebl> You could write an upstart job which runs at "start on stopped rc2"
[12:44] <mbiebl> This means, it is started after runlevel has been started completely, which means, the mythtv backend should be running.
[12:44] <Shred01> ahhh.  after all of the initscripts are run.
[12:44] <Shred01> right.
[12:45] <mbiebl> correct.
[12:49] <Shred01> is upstart-for-everything supposed to happen in gutsy or post-gutsy?
[01:11] <mbiebl> Shred01: I guess that not all services will be converted for gutsy but only the main ones.
[01:11] <Shred01> cool enough i guess