This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Rsync: found the problem
- To: cygwin <cygwin at cygwin dot com>
- Subject: Re: Rsync: found the problem
- From: Corinna Vinschen <cygwin at cygwin dot com>
- Date: Fri, 3 Aug 2001 19:07:41 +0200
- References: <610A1F4808E9D411888F0001023F6361A2EC@MUCX> <3B46E116.20508.C8E5ACB@localhost> <20010707095422.C7298@redhat.com> <3B499BF7.6D8FCABC@hplb.hpl.hp.com> <20010709222226.A16128@cygbert.vinschen.de> <3B6960FA.8099DD72@hplb.hpl.hp.com> <3B6A943A.10E925C8@hplb.hpl.hp.com>
On Fri, Aug 03, 2001 at 01:08:26PM +0100, Bill Petheram wrote:
>
> What seems to happen is that rsh reads from stdin. rsh sets stdin to be
> O_BINARY. However in _read (syscalls.cc) the wait flag is NOT set, so
> _read returns -1 and EAGAIN. So stdin for rsh has been set to no delay,
> probably by rsync.
>
> What are the rules for inheriting flags and socket options across forks?
sockets are copied across forks using a Winsock2 copy mechanism
WSADuplicateSocket
WSASocket
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/