Goswin von Brederlow wrote:
Helmut Wollmersdorfer <[EMAIL PROTECTED]> writes:
I would not like to have it on 7/24 servers. There could be problems after longer power outages in combination with weak scripts (which use dates as file names). But this "should be the minority". And such logic will even have problems without anacron.
How will that be a problem? They will run once at (shortly after) bootup and end up with a slightly wrong date in the filename.
A real example: A large organisation names the daily logs (each 1-2 GB) of some servers by date. They exactly contain records from 0:00 to 24:00. After transfer to a dedicated server a cron job uses 'date --date=yesterday' and 'find' to start an analyzing script. anacron cannot solve this, but it will not damage something (just result in some error messages, and/or unnecessary CPU hours in worst case). To make this anacron-proof would need complex bookkeeping and exception handling.
Helmut Wollmersdorfer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
