Hi, Am 06.04.2014 09:05, schrieb Guido Berhoerster:
* Cristian Rodríguez <crrodriguez@opensuse.org> [2014-04-05 02:57]:
- It continues to run just like "cron.daily" with the following bonus perks:
No it doesn't, right now it is possible to run all the housecleaning in cron.daily at a convenient DAILY_TIME now some jobs do not obey that any more and stuff gets spread out between cron and systemd and each systemd timer has to be configured indiviually.
* Log rotation will be postponed until your are connected to AC power, in order not drain your precious battery time.
That would be possible with cron using on_ac_power but I don't think it is a good idea to skip rotating logs.
* The task will run as soon as possible in case your system was turned off, suspended or otherwise inactive at the time the process was scheduled (requires systemd 212 or later)
* If any error is found, the results will be found in the journal (and/or syslog if installed) to see what's going on issue:
systemctl status logrotate.service logrotate.timer
That's actually the worst regression of all, if something like logrotate bombs out I want to get notified immediately via email and not have to poll every box, that's insane. This has so severe regressions for no gain at all and should never even have passed Factory review.
When I first read the heads up I was thinking that this makes sense but after some discussion it turned out that important features went away with that. So I'm really wondering to which magnitude we want to allow that all the time? It happened so often in the past and sometimes if we were lucky after quite some time (sometimes years) we were back to feature parity. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org