Start of systemd timers after install/update of a package

["Jóhann B. Guðmundsson"]

On 01/24/2013 05:31 PM, Jochen Schmitt wrote:
> On Thu, Jan 24, 2013 at 04:53:01PM +0100, Michal Schmidt wrote:
>
>> Was the timer unit active? What does "systemctl status yourunit.timer" show?
> I think, this is a good hint, systemctl status innd-expire.timer told
> me something like
>
> Active: inactive...
>
> After I have done a
>
> # systemctl start innd-expire.timer
>
> I have got a
>
> Active: active (waiting) since ...
>
> So I assume the resolution is to add a
>
> systemctl start/try-restart forbar.timer
>
> in the post and postun scriptlets.
>
> A additonal question of this expirience is, how does systemd
> determinate that a timer should be active after boot.
>
> As a conclusion of my expiriences, I think we need anythin
> as a guideline for this topic.

Yeah the packaging part of this has not been sorted out yet.

I was going to migrated couple of cron jobs and do some local testing 
before proposing something to FPC

JBG