On 1/17/25 11:20 AM, Tomasz Pala wrote:
On Thu, Jan 16, 2025 at 19:29:28 +0100, Thomas HUMMEL wrote:
I thought in my case it did not work because journald showed a
dependency error but, with systemd on debug mode I could see it was an
For the future: if you need to see expanded (%s) and coale
On Thu, Jan 16, 2025 at 19:29:28 +0100, Thomas HUMMEL wrote:
> I thought in my case it did not work because journald showed a
> dependency error but, with systemd on debug mode I could see it was an
For the future: if you need to see expanded (%s) and coalesced (dropins)
"final" service config
On 1/16/25 4:29 PM, Lennart Poettering wrote:
On Do, 16.01.25 11:31, Thomas HUMMEL (thomas.hum...@pasteur.fr) wrote:
Hello,
Is the %i (or %I) specifier supposed to be valid for a template service unit
for the Require= and After= directives ?
It does not seem so in my tests
Documentation state
On Do, 16.01.25 11:31, Thomas HUMMEL (thomas.hum...@pasteur.fr) wrote:
> Hello,
>
> Is the %i (or %I) specifier supposed to be valid for a template service unit
> for the Require= and After= directives ?
> It does not seem so in my tests
>
> Documentation states:
> "you may use the special "%i" sp
Hi,
systemd itself already uses them in those sections without problems so they
should definitely work:
systemd-zram-setup@.service:After=dev-%i.device
systemd-journald@.service:Requires=systemd-journald@%i.socket
systemd-journald-varlink@%i.socket
systemd-journald@.service:After=systemd-journald@
Hello,
Is the %i (or %I) specifier supposed to be valid for a template service
unit for the Require= and After= directives ?
It does not seem so in my tests
Documentation states:
"you may use the special "%i" specifier in many of the configuration
options" but don't seem to detail which one e
