As a follow up on this, I just found that the problem with the Win32 native version of unison described in
http://cygwin.com/ml/cygwin/2004-09/msg01131.html is also a consequence of the new pipe code. The hang only happens with the new code, with the old pipe code it works fine. And Karl seems to be right, it only happens on XP SP2. He tested on W2K and XP pre SP1, I just tested on NT4 SP6 and could verify that it works fine there, too. That's really weird. Corinna On Sep 14 11:10, Corinna Vinschen wrote: > On Sep 13 14:09, Bob Byrnes wrote: > > On Sep 12, 4:42pm, Corinna Vinschen wrote: > > -- Subject: Re: [Fwd: 1.5.11-1: sftp performance problem] > > This all works most of the time. But it interacts badly with the > > POSIX atomic write requirements related to PIPE_BUF. In particular, > > select should say that a pipe is not writable when there is < PIPE_BUF > > space available (and our implementation does this). > > I reread the description of CreateNamedPipe in MSDN and now I'm wondering > if exactly that, trying to mimic POSIX atomic writes, is the culprit of > the problem. MSDN states: > [...] -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
