[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:25:05 -0400

>From address@hidden  Thu Feb 15 02:59:54 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 02:59:52 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14T6Au-00061Q-00; Wed, 14 Feb 2001 12:57:08 -0500
Received: from ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14T69w-00060E-00
        for <address@hidden>; Wed, 14 Feb 2001 12:56:08 -0500
Received: from ( [])
        by (8.9.1/8.9.1) with ESMTP id MAA08490;
        Wed, 14 Feb 2001 12:56:02 -0500 (EST)
Received: from (address@hidden [])
        by (8.8.6 (PHNE_17190)/8.8.5) with ESMTP id MAA27011;
        Wed, 14 Feb 2001 12:55:59 -0500 (EST)
Received: (from address@hidden)
        by (8.9.0/8.9.0) id MAA00788;
        Wed, 14 Feb 2001 12:55:23 -0500 (EST)
Message-Id: <address@hidden>
Subject: Re: pserver causes slow serialization
To: address@hidden
Cc: address@hidden, address@hidden
In-Reply-To: <address@hidden> from "address@hidden" at Feb 14, 1 04:22:29 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 12:55:22 -0500 (EST)
Status: O
Content-Length: 817
Lines: 23

address@hidden writes:
> Looking at the source
> I'm thinking that the parent part of the cvs-pserver is not wait(2)ing for
> it's child until it see the
> pipes closed. To that end I've done various thing with redirecting
> stdin/stdout/stderr to no avail.

That's correct.  There was a bug that caused the pipes to not be closed
on exec, so they get inherited by any child processes and the parent
ends up waiting when it shouldn't.  That's fixed in the current
development version and it seems to be reasonably stable if you want to
try it.  (See for details of how to get it if you don't
already know.)

-Larry Jones

I'm so disappointed. -- Calvin

Info-cvs mailing list

reply via email to

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