[arch-dev-public] Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?

[Thomas Bächler]

Am 01.04.2014 16:44, schrieb Thomas Bächler:
> Am 29.03.2014 08:52, schrieb Thomas Bächler:
>> Am 28.03.2014 22:26, schrieb Thomas Bächler:
>>> Am 28.03.2014 01:01, schrieb Thomas Bächler:
>>>> core/logrotate 3.8.7-1          /etc/cron.daily/logrotate
>>>> core/man-db 2.6.6-1             /etc/cron.daily/man-db
>>>> core/mlocate 0.26-1             /etc/cron.daily/updatedb
>>>> core/shadow 4.1.5.1-7           /etc/cron.daily/shadow
>>>> extra/pkgstats 2.3-3    /etc/cron.weekly/pkgstats
>>>
>>> After the overall positive response, I converted these. Since none of my
>>> machines used any cron jobs, I uninstalled cronie from them.
>>
>> I am not sure how this interacts with suspend. My laptop was suspended
>> at midnight, and on resume two of my timers fired, but 3 didn't. Maybe
>> this is because interaction with suspend is broken, mabe because of
>> AccuracySec set to 12h. I need to investigate this issue further.
> 
> *shrugs* Seems to work just fine now. All timers fired when I resumed at
> work today.

Okay, this should stay in testing for the moment.

There's a case where the persistent timer *never* run until your machine
is running just at the right moment. I prepared a patch for this
problem, just need to test and submit it tonight.

I also forgot to set the PACKAGER variable on this machine, so the
packages have "Unkown packager", I should probably rebuild the packages
soon, then.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-dev-public/attachments/20140402/e7b4fb3c/attachment.asc>