>> The third.service started as soon as *either* the first.target or
>> second.target was started, even though it has *both* of them as
>> Requisites, and as previously quoted, the manual,
>> https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Req
>> uisite
>> =, says:
>> | Requ
Lennart Poettering wrote:
> Martin wrote:
>> Ah. Thanks for the explanation. Adding
>> Wants=first.target second.target
>
> Hmm, what?
>
> After=/Before= are the ordering deps, Wants= is a requirement dep.
>
>> Respectfully suggest that the documentation bug should be fixed!
>
>I am sorry, what?
Andrei Borzenkov wrote:
>> It has noticed and logged that one of the Requisite targets for the
>> Third service isn't active, but it starts it anyway :-(
>>
>> That seems to go directly against the documented behaviour (at
>> https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Req
Perhaps I'm missing something, but that's still not doing what I expect.
Here's what I have...
#- /etc/systemd/system/first.target -#
[Unit]
Description=Started first
Wants=third.service
#- /etc/systemd/system/second.target -#
[Unit]
Description=Started second
Wants=third.service
Hi
I have two "primary" services running on a Linux server with `systemd` that
may be started at approximately the same time, or could just as easily be
started days apart. When started, they take a few seconds to reach "ready"
state, and can signal that readiness however I choose.
I have a third
