It isn't my client I'm concerned about, it's server-to-server mainly. At the time of writing this message, these are the timestamps on all the servers (done by executing a series of
/time servername in rapid succession):
LethalEncounter.eqemulator.net:
Monday May 23 2005 -- 11:54 -05:00
(This one is correct for Central Time. I should know -- I'm in Texas with him
And it seems to be synced up with true USNO time too -- as his clock is right on with my PC's. I would expect no less from a military man
)
irc.eqemulator.net
Monday May 23 2005 -- 12:54 -04:00
(So this one's been fixed now. Thanks Dood/FNW/Krusher
It's an hour ahead of Lethal but it should be cuz this one's on Eastern time - note the -04:00)
stewie.eqemulator.net
Monday May 23 2005 -- 11:54 -04:00
(11:54 and Eastern time?! WTF?! no.)
rogean.eqemulator.net
Monday May 23 2005 -- 11:53 -04:00
(11:53 and Eastern time?! no. Also, it might sound petty to nitpick about you being 1 minute off from the rest, but read the FAQ below and you see that even 1 minute off might cause some issues from time to time. Although, until you correct the hour or timezone, in the eyes of some of the servers you are 1h1m off.)
services.eqemulator.net
Mon May 23 12:54:55 2005 EDT
(correct)
(stats.eqemulator.net gave no response to a time query)
Quote:
|
Originally Posted by Unreal 2.3 FAQ
Linking - (sync) Possible negative TS split at link server.blah.net (1078875430 - 1078875478 = -4 
If you get such a warning this means your clocks are not synched.
Correct time is VERY important for IRC servers, if the clocks are off for just 20 seconds you may run into trouble already. If your clocks are minutes or even hours off, you are guaranteed to have problems.
To name a few:
- temporary *lines/shuns will not expire correctly, they might expire like an hour earlier (or even directly on add) or later
- sudden (wrong) nick collision kills
- channels might not show up in /LIST (this requires the time to be off by 24h or more)
- more..
Synch the server clock - *NIX
You should run ntpd (=daemon) or ntpdate (=simple util, usually ran via cron) on all your servers.. this is pretty easy to set up and once it's working it should take care of all your worries. Note however that this requires root access.
Synch the server clock - Windows
There are various time synching progs out there (just google), but newer windows versions (XP, 2003) should already do it automatically.
Synch via services or /TSCTL
This can ONLY be used if your clock is off just for like <30 seconds because the ircd may stall [!] till it's synched again. So if you are off for 10 minutes and you use tsctl or services to synch all clients on the ircd MAY BE FROZEN FOR 10 MINUTES! Therefore, be very careful with this command.
About timezones
Note that linking ircds from different timezones is NO PROBLEM because GMT time is used for everything. |
Hybrid Mode
