-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01.03.2015 Andrei Borzenkov wrote:
No. For oneshot services systemd starts service and waits until it is finishes before continuing with any other service that depends on it.
And for notify it waits for the notify before starting other services. At least that is how I understood Cristian's statement.
It is difference between starting long running background services and doing one time job.
What is confusing here?
I'll try to get this straight: With oneshot, systemd waits for the task to *exit* before starting other services that Require/Want/After this task. With notify, systemd waits until it gets notified before starting these tasks. Right so far? In my use case, a long running backup, I could do the notify at the end, when my backup is finished. But the end result would be the same, the following tasks would start when my backup is finished. So I do not see the advantage of using one over the other.
TimeoutStartSec= ... Defaults to TimeoutStartSec= from the manager configuration file, except when Type=oneshot is used, in which case the timeout is disabled by default.
Andrei, these are all very fine and I thank both you and Cristian for your answers. But I still don't get why Cristian would call setting a Timeout (no matter which one) as a hack. Regards, Johannes - -- "NOBODY expects the Spanish Inquisition! Our chief weapon is surprise ... surprise and fear ... fear and surprise ... Our two weapons are fear and surprise ... and ruthless efficiency ... Our *three* weapons are fear, surprise, and ruthless efficiency..." (Monthy Python) -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlTywA8ACgkQzi3gQ/xETbLPNACfQBBsB8VPmZQuV4I4nmBVwU1b ibEAn2Vn9alQnIV63PhMSk0rhVFqrYuM =XyZt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org