Some OS's have very expensive gettimeofday calls.. At 04:04 PM 6/4/2006, kama wrote:
Could this cause choke if the gettimeofday() is really choppy and time consuming? /Bjorn On Sun, 4 Jun 2006, Alfred Reynolds wrote: > Both server engines use the gettimeofday() call to work out elpased > time. If that time moves significantly during a frame then the next > frame will not run properly (you would see a one frame glitch on the > server). If your clock is adjusted once per day then this won't be > noticable but if your clock is constantly wandering the effects could be > seen. > > - Alfred > > Erik Hollensbe wrote: > > On Jun 4, 2006, at 11:37 AM, Gary wrote: > > > >> If you are talking about cumulative clock drifting, yes. As far as > >> it's interaction to hlds etc, I don't know :) > >> I know the quartz is sensitive to temperatures and if it gets too > >> warm/BIOS issue, it will drift more. > > > > Sorry, I meant the daemons. The clock drift isn't the issue, safely > > updating the time on the box is. :) > > > > Hopefully Alfred can chime in on this topic monday. > > > > -- > > Erik Hollensbe > > [EMAIL PROTECTED] > > > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list > > archives, please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
