On 5/10/2011 6:55 AM, Martin Pitt wrote:
I don't think we can, given that upstart and systemd have opposite
approaches to when to start services ("as soon as you can" vs. "not
until you need them"). So even a very coarse approximation like
I don't think this is correct. If I understood the introduction
correctly, you have the choice of either "as soon as you can" or "not
until you need them". systemd creates the socket either way, and then
is either configured to start the daemon in parallel with daemons that
depend on it, or only start the daemon when something actually connects
to the socket. Which is up to you when you write the config.
If you choose the delayed start option, then yes, a test that checks
what processes are running would fail, but a test that checks for the
actual availability of the service would not.
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
