El 06/04/14 04:05, Guido Berhoerster escribió:
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.
There is no global equivalent to DAILY_TIME in the systemd configuration.. I sincerly hope that idea is not carried forward in time, since I do not believe this is desirable design to follow.
* 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.
run-crons already quits when the system is on battery.. # # Don't run jobs on laptops, that are AC-offline # if test -x /usr/bin/on_ac_power ; then on_ac_power -q if [ "$?" = "1" ]; then exit 0 fi fi
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.
Since a long time cron no longer requires an SMTP service running on the box and logs to syslog instead.. many people are already not getting email..
This has so severe regressions for no gain at all and should never even have passed Factory review.
Since many upstream projects are slowly moving away from having their own logs to rotate most recently GDM and the X server and instead will start logging to the journal, I will ask for this logrotate change to be reverted and work towards making it unnecessary instead. Next time you see run away cron scripts (yes they escape cron control all the time, try starting a forking daemon from crontab :-D) , hijack port 25.. you will understand why I tried to bring some sanity just to once again hit the wall of tradition. -- Cristian Team PITA -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org