[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(no subject)

From: root
Subject: (no subject)
Date: Mon, 13 Aug 2001 05:21:47 -0400

>From address@hidden  Thu Feb 15 06:27:23 2001
>Return-Path: <address@hidden>
Received: from ( [])
        by (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
        for <address@hidden>; Thu, 15 Feb 2001 06:27:20 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14T9PG-0003k6-00; Wed, 14 Feb 2001 16:24:10 -0500
Received: from ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14T9Nh-0003j6-00
        for <address@hidden>; Wed, 14 Feb 2001 16:22:33 -0500
Received: from ( [])
        by (8.9.1/8.9.1) with ESMTP id QAA06648;
        Wed, 14 Feb 2001 16:22:25 -0500 (EST)
Received: from (address@hidden [])
        by (8.8.6 (PHNE_17190)/8.8.5) with ESMTP id QAA24877;
        Wed, 14 Feb 2001 16:22:24 -0500 (EST)
Received: (from address@hidden)
        by (8.9.0/8.9.0) id QAA05822;
        Wed, 14 Feb 2001 16:22:25 -0500 (EST)
Message-Id: <address@hidden>
Subject: Re: Timestamp race avoidance in do_update()
To: address@hidden (Laine Stump)
Cc: address@hidden
In-Reply-To: <address@hidden> from "Laine Stump" at Feb 14, 1 03:47:01 pm
From: address@hidden (Larry Jones)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: address@hidden
Errors-To: address@hidden
X-BeenThere: address@hidden
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:address@hidden>
List-Post: <mailto:address@hidden>
List-Subscribe: <>,
List-Id: Announcements and discussions for the CVS version control system 
List-Unsubscribe: <>,
List-Archive: <>
Date: Wed, 14 Feb 2001 16:22:24 -0500 (EST)
Status: O
Content-Length: 1537
Lines: 35

Laine Stump writes [quoting me]:
> > 
> > Unfortunately, usleep() isn't portable.
> Okay, then how about nanosleep()?

nanosleep() is even less portable.  (It's part of the POSIX real-time
extensions.  I think usleep() is part of the base POSIX standard;
sleep() definitely is and it's been in Unix "forever" so it's much more
widely implemented.)

> Aside from the basic extra duty of keeping track of multiple files at
> once rather than cycling through a list, each commit for each file has
> a different log comment, so multiple commits *can't* be done with a
> single invocation of cvs. (I take that back - I suppose I could save
> all log comments, then go back and change them later with a long
> string of "cvs admin -m<rev>:<message> <file>" commands, but that
> makes the script even more complex and memory intensive, and we must
> remember that I'm a lazy programmer, who would rather change one sleep
> to nanosleep() than to write a ton of confusing perl ;-)

You could always have the script talk directly to a CVS server using the
client/server protocol -- since the server no longer sleeps, that would
avoid the problem.  You could also run the CVS commands in the
background so you don't have to wait for the sleep before continuing
(although you may end up waiting on your own locks in that case).

-Larry Jones

There's never enough time to do all the nothing you want. -- Calvin

Info-cvs mailing list

reply via email to

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