On Wed, Dec 16, 2020 at 03:05:05PM +0200, Topi Miettinen wrote:
> On 16.12.2020 12.03, Ulrich Windl wrote:
> > > > > Jarkko Sakkinen schrieb am 15.12.2020 um 05:19 in
> > Nachricht
> > <20201215041903.ga21...@kernel.org>:
> > > On Mon, Dec 14, 2020 at 08:25:50AM +0100, Ulrich Windl wrote:
> > > >
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,
> https://www.fre
On Di, 22.12.20 18:48, Joe Pater (02joepate...@gmail.com) wrote:
> kernel-install seems to be making a mistake generating my
> grub.cfg:
The kernel-install script shipped with systemd has nothing to do with
grub. Your distro's downstream package probably has a script that
plugs into that. Hence c
Buenos dias;
en el shell export Variable para que tome los cambios.
El mar, 22 dic 2020 a las 14:48, Joe Pater (<02joepate...@gmail.com>)
escribió:
> kernel-install seems to be making a mistake generating my
> grub.cfg:
>
>
> kernelopts="root=/dev/mapper/fedora_localhost--live-root=/dev/mapper/
kernel-install seems to be making a mistake generating my
grub.cfg:
kernelopts="root=/dev/mapper/fedora_localhost--live-root=/dev/mapper/fedora_localhost--live-root=/dev/mapper/fedora_localhost--live-root=/dev/mapper/fedora_localhost--live-root=/dev/mapper/fedora_localhost--live-root=
And so on -
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 docum
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 uni
In addition to what Mantas said, I'd suggest reading man systemd.special.
and https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
This should give you an idea what network-online.target is supposed to be.
It's not a target to hook arbitrary services into (via WantedBy).
Your service l
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
>> https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Req
On Tue, Dec 22, 2020 at 1:36 PM Ronald Wimmer wrote:
> On a server running OL 7.9 with SystemD 219 we have a custom SystemD
> service we have something like
>
>
> [Unit]
> Requires=network.target docker.service
>
> [Service]
> Restart=always
> RestartSec=10
> TimeoutSec=300
> WorkingDirectory=/da
On a server running OL 7.9 with SystemD 219 we have a custom SystemD
service we have something like
[Unit]
Requires=network.target docker.service
[Service]
Restart=always
RestartSec=10
TimeoutSec=300
WorkingDirectory=/data/someapplication
ExecStartPre=
ExecStart=
ExecStop=
ExecStopPost=
[Inst
13 matches
Mail list logo
