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

[Freeciv-Dev] Re: (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]
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#2305) Add check to test for a working gettimeofday
From: "Raimar Falke via RT" <rt@xxxxxxxxxxxxxx>
Date: Tue, 12 Nov 2002 23:14:33 -0800
Reply-to: rt@xxxxxxxxxxxxxx

On Tue, Nov 12, 2002 at 11:02:15PM -0800, Jason Short via RT wrote:
> 
> [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?

time() is used. Smaller accuracy but working.

> Can you provide code that uses this check?

The autoconf test?!

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
  +#if defined(__alpha__) && defined(CONFIG_PCI)
  +       /*
  +        * The meaning of life, the universe, and everything. Plus
  +        * this makes the year come out right.
  +        */
  +       year -= 42;
  +#endif
    -- Patch for 1.3.2 (kernel/time.c) from Marcus Meissner



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