Charles Hedrick via FreeIPA-users freeipa-users@lists.fedorahosted.org writes:
it's active, but it seems not to do anything:
● ipa-ccache-sweep.timer - Remove Expired Kerberos Credential Caches Loaded: loaded (/usr/lib/systemd/system/ipa-ccache-sweep.timer; enabled; vendor preset: disabled)
I believe the intent is that it should run every 12 hours. It doesn't seem to be doing so. From a web discussion:
That's the same on my system... I did enable and start the timer with my local ansible plav - but that only worked for the current boot.
OnUnitActiveSec does indeed refer to the time since the service referred to by the timer has run. But if you only use OnUnitActiveSec and no other trigger then issue the command to start or enable foo.timer, foo.service will never run. Why would it, no trigger would ever be activated in the first place: something needs to trigger the first run of foo.service in order to for you to ever have 3 seconds pass since it was last run.
So in other words, OnUnitActiveSec can be used to define the interval between repetitions, but another trigger (like OnActiveSec or OnBootSec) would be needed to trigger the first run of foo.service to get the ball rolling.
In other words: you must also enable the /usr/lib/systemd/system/ipa-ccache-sweep.service. That way it will run once at system reboot and later every 12 hours. I've just changed my playbook and I'll see with the next reboot how that works out.
Jochen
Ok. Makes sense. I’ll use that solution too.
On Aug 14, 2022, at 4:35 PM, Jochen Kellner jochen@jochen.org wrote:
Charles Hedrick via FreeIPA-users freeipa-users@lists.fedorahosted.org writes:
it's active, but it seems not to do anything:
● ipa-ccache-sweep.timer - Remove Expired Kerberos Credential Caches Loaded: loaded (/usr/lib/systemd/system/ipa-ccache-sweep.timer; enabled; vendor preset: disabled)
I believe the intent is that it should run every 12 hours. It doesn't seem to be doing so. From a web discussion:
That's the same on my system... I did enable and start the timer with my local ansible plav - but that only worked for the current boot.
OnUnitActiveSec does indeed refer to the time since the service referred to by the timer has run. But if you only use OnUnitActiveSec and no other trigger then issue the command to start or enable foo.timer, foo.service will never run. Why would it, no trigger would ever be activated in the first place: something needs to trigger the first run of foo.service in order to for you to ever have 3 seconds pass since it was last run.
So in other words, OnUnitActiveSec can be used to define the interval between repetitions, but another trigger (like OnActiveSec or OnBootSec) would be needed to trigger the first run of foo.service to get the ball rolling.
In other words: you must also enable the /usr/lib/systemd/system/ipa-ccache-sweep.service. That way it will run once at system reboot and later every 12 hours. I've just changed my playbook and I'll see with the next reboot how that works out.
Jochen
-- This space is intentionally left blank.
freeipa-users@lists.fedorahosted.org
-
Charles Hedrick -
Jochen Kellner