>> 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:
>> |
On Di, 22.12.20 15:24, freedesk...@priatel.co.uk (freedesk...@priatel.co.uk)
wrote:
65;6200;1c
> 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,
>
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?
On Di, 22.12.20 13:18, freedesk...@priatel.co.uk (freedesk...@priatel.co.uk)
wrote:
> 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
On Mo, 21.12.20 21:18, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> You miss ordering dependencies. Neither Requires not Requisite work
> without proper After/Before.
>
> systemd manuals make impression that dependencies are between units.
> This is wrong - dependencies are between jobs. If
On Mo, 21.12.20 17:23, freedesk...@priatel.co.uk (freedesk...@priatel.co.uk)
wrote:
> 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
>
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
>>
dering both jobs (verify state of
unit A and start unit B) run concurrently and the order is
non-deterministic (or may be it is but then it is always "wrong" for
your purpose :) ), so in your case job for Second runs too late, when
Third is already started and there is no pending job to fail
Sent: 21 December 2020 15:32
To: freedesk...@priatel.co.uk
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Services with multiple pre-requisites
On Mo, 21.12.20 14:43, freedesk...@priatel.co.uk (freedesk...@priatel.co.uk)
wrote:
> Hi
>
> I have two "prim
On Mo, 21.12.20 14:43, freedesk...@priatel.co.uk (freedesk...@priatel.co.uk)
wrote:
> 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
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
11 matches
Mail list logo
