Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 15 Jan 2003 16:53:52 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: Re: setting socket option SO_RCVTIMEO doesn't affect blocking behavio r of recvfrom
Message-ID: <20030115155352.GV1373@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
References: <3B2480653E7D2C4E8AA5699598D691C429FF74 AT xch-se-03 DOT se DOT nos DOT boeing DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B2480653E7D2C4E8AA5699598D691C429FF74@xch-se-03.se.nos.boeing.com>
User-Agent: Mutt/1.4i

On Wed, Jan 15, 2003 at 09:40:55AM -0600, Lane, Frank L wrote:
> Wanting to keep things as simple as possible I thought of using setsockopt
> to force a 10 second timeout on the blocking call to recvfrom.  The level
> used was SOL_SOCKET and the option was SO_RECVTIMEO with the time struct
> loaded with a 10 for the seconds member.  The behavior of the application
> appears unchanged by the call to setsockopt.
> [...]
> Any help will be appreciated.

SO_RECVTIMEO isn't supported by WinSock, unfortunately.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT 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/