[email protected] said: > >We could easily and cleanly bypass the code that uses utmpx. That would > > screwup accounting if time stepped by more than a second.
> I'm not entirely clear on the referent of "that". The *bypass* would screw > up accounting if time stepped by more than a second? I assume the time-changed info is used by accounting programs. Without that info, any accounting and possibly billing data for the time logged in will be off one way or the other if the time gets stepped while you are logged in. Normally, time is only stepped when ntpd is first run at boot time, and even then it's often under a second. You can test your system by grepping your /var/log/messages or /var/log/syslog for "clock_step". Look in something like /var/log/ntp/ntpd.log if your ntp.conf puts logging in a separate file. ---- Joel says RTEMS doesn't support utmpx.h so I'll start by making that case build. But you are right. It was ifdefed out in ntp classic so I won't bother to recover the utmp (no x) case. Does buildbot have an OpenBSD machine? Do we have a way to test on RTEMS? -- These are my opinions. I hate spam. _______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
