On Tue, 2011-06-21 at 01:54 +0200, Reindl Harald wrote: > > Am 21.06.2011 01:38, schrieb Lennart Poettering: > > On Tue, 21.06.11 01:33, Reindl Harald (h.reindl@xxxxxxxxxxxxx) wrote: > > >> useless as long it fires them up as fast as possible and at the same time > >> so you need socket activation, so you need native services > > > > This is a misunderstanding. If A is ordered after B, then systemd spawns > > A, waits until A is finished with start-up and only then starts B. If > > the order between MySQL and your service is available and correct, then > > things will work correctly for you. > > how do you define "finished with startup"? When the init script completes and returns. That's how it's always been defined. How else could an init system possibly define it? > what does our baby aka systemd know about what happens inside the service? Not a lot. Neither does any other init system. What do you think is new here? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
