Scott James Remnant wrote: > On Thu, 2008-11-06 at 16:05 +0100, Harald Hoyer wrote: > >>>> With the current implementation I see the following problems: >>>> - the job description files are very static. Dependencies can only be >>>> added, >>>> modified, deleted by modifying this one job file (not package friendly) >>>> >>> This is an ongoing discussion: what ideas do you have? >>> >>>> - there is no dependency like "start me before service xyz" >>>> >>> 0.3/0.5: >>> start on starting syz >>> ~~~ >> which really starts syz only if the other job is started? >> >> like: >> >> network: >> start on starting ldap-client >> start on starting mount-nfs-filesystems >> > The difference between starting and started is quite subtle, but very > important. > > "starting" is emitted when the job is given the "start" command, but > _before_ any scripts or execs are run > > "started" is emitted *after* all of the scripts or exces (including the > main one) have been run. > > And, most importantly, "starting" *waits* for your job to finish before > continuing. > > foo: > start on starting bar > exec sleep 20 > > bar: > exec echo woo > > start bar > *20 seconds later* > woo
ah :) very nice, exactly what we need here. > >>>> - turning a job/service off requires removing the job file, which may >>>> be solved >>>> by symlinks? >>>> >>> Again an ongoing discussion: what ideas do you have? >>> >>> Do you want to disable it from automatic starting, or prevent manual >>> starting as well? >> both >> > How is that any semantically different from deleting the job? Deleting a symlink would be ok.. deleting the original jobfile provided by an rpm would not. > > Why do you want to disable it? e.g. I don't want to remove the rpm package, but I want all scripts with "/sbin/start service-xyz" to fail. -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
