Hi!
I wrote some services that should run when booting and some time after
booting.
As it seems the service to run during boot works, but the timer-triggered one
does not.
I have no idea why.
Here are the details:
# systemctl status prevent-fencing-loop.service
● prevent-fencing-loop.service - Pr
On Mon, Mar 7, 2022 at 11:22 AM Ulrich Windl <
ulrich.wi...@rz.uni-regensburg.de> wrote:
> Hi!
>
> I wrote some services that should run when booting and some time after
> booting.
> As it seems the service to run during boot works, but the timer-triggered
> one
> does not.
> I have no idea why.
>
[Install]
WantedBy=timer.target
It's supposed to be timers.target
>>> Mantas Mikulenas schrieb am 07.03.2022 um 10:39 in
Nachricht
:
> On Mon, Mar 7, 2022 at 11:22 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> Hi!
>>
>> I wrote some services that should run when booting and some time after
>> booting.
>> As it seems the service to run durin
On Mo, 07.03.22 12:24, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> Thanks for that. The amazing things are that "systemd.analyze verify" finds no
> problem and "enable" virtually succeeds, too:
Because there is no problem really: systemd allows you to define your
targets as you like
>>> Lennart Poettering schrieb am 07.03.2022 um 14:08
in
Nachricht :
> On Mo, 07.03.22 12:24, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Thanks for that. The amazing things are that "systemd.analyze verify" finds
> no
>> problem and "enable" virtually succeeds, too:
>
> Becaus
Hi,
It seems that PrivateNetwork=yes is a memory consuming directive. The kernel
seems to allocate quite an amount of memory for each service (~50 kB) that has
this directive enabled. I wonder if this is expected and if anyone has had
similar experience?
Is there any ways to reduce the usage
