On Friday 26 May 2006 07:59, Andreas Jaeger wrote:
3. ZMD scheduling seems to be a bit broken now. It appears that the service refresh happens at the same time as the hourly maintenance, even though it is scheduled for the next day. Once the full service refresh and maintenance has run ( hourly by default it seems ) the schedule is reset with an updated time for the service refresh 24 hours later and 1 hour later for the maintenance. Of course the service refresh still happens one hour later and another new time i scheduled for it.
This has the side effect of a full service refresh will run if my system is booted outside of the hourly maintenance window, parse-metadata and update-status hogging 100% CPU for a few minutes on boot. If i reboot my system inside the hourly maintenance window this does not happen.
Please file a bug against the component "ZENworks",
Thanks, Andreas
#179042 The archive atached to this bug filing contains zmd-messages.log, zmd-backend.log and zmd.conf These logs were started fresh and ZMD was left to run for an hour or so without any package management interaction with rug or zen-updater. Cheers Graham