On 10/11/06, Marcy Cortes <[EMAIL PROTECTED]> wrote:
Sure, it wastes a little, but it doesn't look that bad here (we have to run NTP on every server to sync security tickets and stuff). Velocity reports the idle ones at 0.01% of a CPU, and that's with their agent presumbaly doing a little stuff too).
IIRC the NTP mechanism was to review adjusting the change of the drift every 2 seconds or so. Even though this is very little work, it does make VM think the guest is busy and keeps it in queue. Asking the snmp agent every minute for some MIBs (when the guest did real work) is an order of maginute less annoying for VM. I think the Kerberos stuff requires same time within 30 seconds. That's not a very strong requirement and could allow for some drift. If your applications can afford stepping back time a little, then an ntpd -q via cron might be good enough. Having ETR steer the LPAR TOD clock is nice because it compensates the drift for you. Combining ETR and NTP is not good because the model behind ntpd does not match ETR. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
