Re: User/Group overrides in a templated service triggered via timer

[Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>]

On Mon, Aug 31, 2020 at 04:20:13PM -0400, Kevin P. Fleming wrote:
> Did you also create an instance of the timer with the same instance
> suffix? I've got a configuration working like that and it works fine.
> If you don't want to do that, you can explicitly configure the name of
> the service to be triggered (in the timer unit) instead of relying on
> the timer/service names matching.

Responding to myself, it seems that my problem was that I created the 
drop-in conf file as:

/etc/systemd/system/grok-fsck@foo.d/10-runas.conf

However, for the override to properly apply, it needed to be in:

/etc/systemd/system/grok-fsck@foo.service.d/10-runas.conf

I think without the "service" part in the directory name it was not 
properly found by the timer-triggered service run.

-K
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel