Complete.Org: Mailing Lists: Archives: freeciv-dev: November 2002:
[Freeciv-Dev] (PR#2305) Add check to test for a working gettimeofday
Home

[Freeciv-Dev] (PR#2305) Add check to test for a working gettimeofday

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: rf13@xxxxxxxxxxxxxxxxx
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] (PR#2305) Add check to test for a working gettimeofday
From: "Jason Short via RT" <rt@xxxxxxxxxxxxxx>
Date: Tue, 12 Nov 2002 23:02:15 -0800
Reply-to: rt@xxxxxxxxxxxxxx

[rfalke - Mon Nov 11 18:54:43 2002]:

> 
> To ensure basic sanity we need to test the gettimeofday a bit
> harder. So at Thomas's system it prints out:
> 
> after 0.157977s: going backward by 188us
> after 0.245779s: going backward by 190us
> after 0.007114s: going forward by 4295s
> after 0.106756s: going backward by 189us
> after 0.137305s: going backward by 185us
> after 0.097206s: going backward by 190us
> 
> we want to detect such systems.

I don't entirely see what the purpose of such detection is.

The only thing you can do is to disable PING packets for servers
compiled on such a system.  Or can you try to "estimate" PING time even
if gettimeofday doesn't work perfectly?

Can you provide code that uses this check?

jason




[Prev in Thread] Current Thread [Next in Thread]