Re: [Patch] To handle Win32 pipe names

Stephen, On May 17 12:57, Stephen Cleary wrote: > Attached is a patch against the current CVS sources, with a ChangeLog. This > patch allows Win32 pipe names to be opened as files. that's still not quite what I had in mind. I'd like to see as less special windows path handling in Cygwin as poss

Re: [Patch] To handle Win32 pipe names

On Wed, 19 May 2004, Corinna Vinschen wrote: > So that explains your patch to symlink_info::check. But it's not > exactly right to circumvent this only for pipes. Any \\.\foo path > should get the same handling. Wouldn't it be more straightforward to > use is_unc_share or a slightly modified ve

Re: [Patch] To handle Win32 pipe names

On May 19 10:08, Brian Ford wrote: > On Wed, 19 May 2004, Corinna Vinschen wrote: > > > So that explains your patch to symlink_info::check. But it's not > > exactly right to circumvent this only for pipes. Any \\.\foo path > > should get the same handling. Wouldn't it be more straightforward to

Question concerning SSHD on CYGWIN

Hello, For a internal prototype we are using cygwin on a windows 2000 system to transfer data via ssh from one windows machine to this windows system with cygwin sshd. If we have alot of data to transfer (e.g. 800 MB) after approximately 10 minutes the transfer hangs without an exception.

Re: Question concerning SSHD on CYGWIN

Wrong list. Please see for details. In the meantime, I've redirected this to the correct one. Please remove cygwin-patches from further discussion on this topic unless you actually submit a patch to Cygwin. Igor On Wed, 19 May 2004, Kleinert