Re: Start of systemd timers after install/update of a package

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

 



Tomas Mraz (tmraz@xxxxxxxxxx) 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. 

Bill
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux