Re: [systemd-devel] LogsDirectory= permissions

2022-04-20 Thread Mantas Mikulėnas
On Wed, Apr 20, 2022, 23:43 Lennart Poettering wrote: > On Mi, 20.04.22 22:18, Andrea Pappacoda (and...@pappacoda.it) wrote: > > > Hi! I've been playing around with various options documented in > > systemd.exec(5) recently, and I'm having an issue with `LogsDirectory=` > and > > its

Re: [systemd-devel] Waiting for (transient) hostname configuration

2022-04-20 Thread Dan Nicholson
On Wed, Apr 20, 2022 at 2:10 PM Alessio Igor Bogani wrote: > > Hi Lennart, > > On Wed, 20 Apr 2022 at 16:47, Lennart Poettering > wrote: > [...] > > > I use systemd-networkd and systemd-networkd-wait-online is enabled but > > > unfortunately it doesn't work anyway. > > If you don't mind I show

Re: [systemd-devel] LogsDirectory= permissions

2022-04-20 Thread Lennart Poettering
On Mi, 20.04.22 22:18, Andrea Pappacoda (and...@pappacoda.it) wrote: > Hi! I've been playing around with various options documented in > systemd.exec(5) recently, and I'm having an issue with `LogsDirectory=` and > its permissions. > > In particular, I've tried setting `LogsDirectory=nginx` for

Re: [systemd-devel] Waiting for (transient) hostname configuration

2022-04-20 Thread Alessio Igor Bogani
Hi Lennart, On Wed, 20 Apr 2022 at 16:47, Lennart Poettering wrote: [...] > > I use systemd-networkd and systemd-networkd-wait-online is enabled but > > unfortunately it doesn't work anyway. If you don't mind I show you one of my Unit files: [Unit] Description=Tango Starter service

Re: [systemd-devel] Waiting for (transient) hostname configuration

2022-04-20 Thread Luca Boccassi
Be very careful about inserting daemon-reload in the boot process, especially early. At best it will cause slow-downs, at worst lock ups. On Wed, 2022-04-20 at 13:18 +, Sietse van Zanen wrote: > Why not add: > > ExecStartPost=systemctl daemon-reload > > to

Re: [systemd-devel] Waiting for (transient) hostname configuration

2022-04-20 Thread Lennart Poettering
On Mi, 20.04.22 12:54, Alessio Igor Bogani (alessio.bog...@elettra.eu) wrote: > > the unit files are *loaded*, i.e. typically at earliest boot, long > > before they are actually *started*. Thus, if you change the hostname > > I understand now. It was the evaluation time of the specifier that I >

Re: [systemd-devel] Waiting for (transient) hostname configuration

2022-04-20 Thread Sietse van Zanen
Why not add: ExecStartPost=systemctl daemon-reload to systemd-networkd-wait-online.service? -Sietse From: systemd-devel on behalf of Alessio Igor Bogani Sent: Wednesday, April 20, 2022 12:54:11 PM To: Lennart Poettering Cc:

Re: [systemd-devel] Waiting for (transient) hostname configuration

2022-04-20 Thread Alessio Igor Bogani
Hi Lennart, On Tue, 19 Apr 2022 at 11:41, Lennart Poettering wrote: [...] > the unit files are *loaded*, i.e. typically at earliest boot, long > before they are actually *started*. Thus, if you change the hostname I understand now. It was the evaluation time of the specifier that I have missed.

Re: [systemd-devel] Antw: [EXT] Re: [systemd‑devel] Waiting for (transient) hostname configuration

2022-04-20 Thread Lennart Poettering
On Mi, 20.04.22 08:16, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > >> Is there a better way? > > > > First of all: % specifiers (including %H) are resolved at the moment > > the unit files are *loaded*, i.e. typically at earliest boot, long > > That's quite some surprise: I thought

[systemd-devel] Antw: [EXT] Re: [systemd‑devel] Waiting for (transient) hostname configuration

2022-04-20 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 19.04.2022 um 11:41 in Nachricht : > On Di, 19.04.22 11:14, Alessio Igor Bogani (alessio.bog...@elettra.eu) wrote: > >> Dear systemd developers, >> >> Sorry for my very bad english. > > Not bad at all. > >> We use the hostname provided by DHCP to start the