Re: [EXT] Re: Re: Re: "OnUnitInactiveSec Timer not firing" issue

["Windl, Ulrich" <u.windl@xxxxxx>]

> -----Original Message-----
> From: systemd-devel <systemd-devel-bounces@xxxxxxxxxxxxxxxxxxxxx> On
> Behalf Of Kevin P. Fleming
> Sent: Tuesday, July 30, 2024 2:57 PM
> Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
> Subject: [EXT] Re:  Re: Re: "OnUnitInactiveSec Timer not
> firing" issue
> 
> On Tue, Jul 30, 2024, at 08:38, Windl, Ulrich wrote:
> > Hi!
> >
> > Top-posting this time:
> > Reading the manual carefully, I recognized an asymmetry:
> > OnActiveSec= defines a timer relative to the moment the timer itself is
> > activated.
> > OnUnitInactiveSec= defines a timer relative to when the unit the timer
> > is activating was last deactivated.
> >
> > Also the manual des not state WHERE that state is remembered.
> 
> Every unit that is kept in memory (some units can be configured to, or
> default to, not being kept in memory when they are stopped) has start, stop,
> and other times kept by systemd. These are visible in 'systemctl list-units',
> 'systemctl status', etc. I've never had a reason to care, but I suspect these are
> not persisted to storage.

 [Windl, Ulrich] 

The details become important after a reboot: Will the time continue as expected, or will it have to be "re-initialized".
Or do I need some special setting in the service unit (Services started by timers are of simple type usually)?