This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Makefile timestamp synchronization problem
- To: Joel Sherrill <joel at OARcorp dot com>
- Subject: Re: Makefile timestamp synchronization problem
- From: Andi Kleen <ak at muc dot de>
- Date: 25 Jul 1998 15:31:33 +0200
- Cc: Jeffrey A Law <law at cygnus dot com>, egcs at cygnus dot com
- References: <Pine.BSF.3.96.980724082647.22717M-100000@vespucci.advicom.net>
Joel Sherrill <joel@OARcorp.com> writes:
> On Fri, 24 Jul 1998, Jeffrey A Law wrote:
>
> > You're not missing anything.
>
> :(
>
> > He's basically hosed. This is precisely why every machine should be
> > running some kind of time sync daemon (xntp for example). Of course
> > I've been too lazy to do this on my machines, so I hit the same problem
> > on occasion.
>
> That's what I thought.
>
> > Usually a few well placed touch commands will clear up the problem for
> > any given build cycle. Of course when they update the sources they'll
> > probably need a few more well placed touch commands.
>
> I can see why this would work but I don't want to get involved in trying
> this one. It is a nightmare.
>
> > ps. I'm just assuming xntp is still the time sync daemon of choice;
> > it's been about 10 years since I worked on network time protocols. Long
> > live the fuzzballs!
>
> Looks like it still is. See http://www.eecis.udel.edu/~ntp/
>
> When I searched the Linux SW Map, that was the only hit on "time
> synchronization".
There is another NTP daemon called 'chrony', which uses a bit less
resources, but it is very new. I think xntpd is still the standard solution.
Also DCE contains its own time service AFAIK, for people who prefer to use
'commercially supported' solutions.
-Andi