Start of systemd timers after install/update of a package

[Michael Scherer]

Le jeudi 24 janvier 2013 à 17:30 +0000, "Jóhann B. Guðmundsson" a
écrit :
> On 01/24/2013 04:28 PM, Bill Nottingham wrote:
> > Tomas Mraz (tmraz at redhat.com) said:
> >> On Thu, 2013-01-24 at 16:03 +0100, Jochen Schmitt wrote:
> >>> Hello,
> >>>
> >>> I have tried to migrating the cron jobs of the inn package to systemd timers.
> >>> Unfortunately, I have got the following problem. After a install/update of the
> >>> package the timer will only start the service unit only once time. The service
> >>> was not started after the configure period was expired. But when I have restart
> >>> the system, it's works as expected.
> >>>
> >>> So I would to ask, what I have to concern when I want to migrate to systemd timers.
> >> I think that massive migration of services from cron to systemd timers
> >> is very premature and should be actively at least discouraged by
> >> packaging directives.
> > I'm somewhat skeptical of the benefit of migration in general. I'm really
> > skeptical that the place you start reducing the dependency load is inn.
> 
> I have started looking into migration of cron jobs to native systemd 
> time units as I mentioned I would do with fesco on the last meeting.
> 
> Out of the total 99 cron job the distribution ship there are 38 which 
> come with service related packages thus might be applicable to migration 
> from my pov the rest should just be left as is.
> 
> What surprised me the most was that none of those components packages 
> depended on cron which was the same thing with rsyslog when I looked 
> into that which is what I expected they would do.
> 
> Maybe it's just me but is there not something more broken/alarming with 
> that or is just me and this is just acceptable from packaging standpoint?