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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
> Sent: Thursday, August 1, 2024 12:49 PM
> To: Windl, Ulrich <u.windl@xxxxxx>
> Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
> Subject: [EXT] Re: Re:  "OnUnitInactiveSec Timer not firing"
> issue
> 
> On Thu, Aug 1, 2024 at 1:42 PM Windl, Ulrich <u.windl@xxxxxx> wrote:
> >
> > Hi!
> >
> > On " Try adding Persistent=yes, it should make it behave as you expect
> (you
> > still need to start the unit manually at least once to initially trigger the
> timer).":
> >
> > You talk about the service unit, and not about the timer unit, right?
> >
> > Systemd.timer says (about Persistent): " Note that this setting only has an
> effect on timers configured with OnCalendar=."
> > So it shouldn't make a difference if the docs are right.
> >
> 
> OK, I missed this, sorry. In this case as far as I can tell the only
> option is to start your unit once after boot. Or just use calendar
> timers? Any reason you need to use OnUnitInactive instead of something
> like OnCalendar=daily?
[Windl, Ulrich] 

Actually systemd has so many features and everybody seemed to use calendar timers, so I wanted to try something else 😉
Now it seems I know why everybody is using calendar timers.
Still (I asked before): What would be useful scenarios for these other timer modes? If there are none, or if the implementation is incomplete, I'd suggest to remove those.
(Expecting people complaining not to remove these, because they found them useful 😉)




[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux