It may take a bit of work, but you could write a small script which invokes and parses "ntpq -c rv localhost" (make sure it actually says localhost when run on the remote machine) and it'll generate a report including such things as the type of time device the machine is synced with *and* the offset of the remote machine with that device.
<example> $ ntpq -c rv localhost assID=0 status=06f4 leap_none, sync_ntp, 15 events, event_peer/strat_chg, version="ntpd [EMAIL PROTECTED] Fri Jul 6 15:02:38 UTC 2007 (1)", processor="x86_64", system="Linux/2.6.21.5", leap=00, stratum=2, precision=-20, rootdelay=0.761, rootdispersion=22.702, peer=40591, refid=REMOTE_TIME_SOURCE, reftime=cba8b3a3.53e79cd7 Thu, Apr 10 2008 15:41:23.327, poll=10, clock=cba8b487.cfeb971a Thu, Apr 10 2008 15:45:11.812, state=4, offset=0.080, frequency=-83.982, jitter=0.004, noise=0.032, stability=0.004, tai=0 A bit of work, but would probably give the best result when looking for the offset. -Trey On Thu, Apr 10, 2008 at 4:08 AM, mikea <[EMAIL PROTECTED]> wrote: > Hi jtaylor, > > You could use the host resources mib to calculate this. There is this mib > entry that you could use: > > HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2008-4-10,10:58:32.0,+0:0 > > You would need a little script or something to calculate the difference > between localtime of the monitoring box (which is connected directly to GPS, > MSF or an Atomic Clock for accurate timekeeping) and the target system. > > Hope this helps. > > Mike > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://community.zenoss.com/forums/viewtopic.php?p=18335#18335 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users >
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
