X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=SE 9nPpJPnSR0CAPe8rzZfWpO+Xu/X9+PK9fd2PXg1vOc/O01QsEn0pK3x02xl80eYE WcZXzZo+USbEcPkZ1HIqceFu434BRhlK1PwMqZDNWMetrYhDrUXtTYy044Gphlv1 LHYTrI2dWJhVb7DmmELKLOIiil6Oq/rik6Q/NXMTs= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=a4wBTxNI mv3pvAQNnoBv0MB6b1E=; b=nB40YkEXBnBxx7FGzYZUDwNPv9BoPJbCI3ajgbQ7 Ns0+bYsihd6/ZkTtuSGlpwqQflD3/FlMHOiNg/l2jzWLxHXdSUbAoCFtCT1wz0Lw khCiuRAOIIMWJSwfemktMouvbZsRuYGWCdBhG7nOed7dg6skhnfMsqZx7hKy/rGw QD8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_40,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RDNS_NONE,SPF_PASS,T_FRT_STOCK2 autolearn=ham version=3.3.1 MIME-Version: 1.0 X-Received: by 10.60.173.235 with SMTP id bn11mr3340553oec.43.1375404118354; Thu, 01 Aug 2013 17:41:58 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 Aug 2013 20:41:58 -0400 Message-ID: Subject: Re: setsockopt support for SO_RCVTIMEO From: Sean Daley To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 On Thu, Aug 1, 2013 at 7:41 PM, Balaji Venkataraman <> wrote: > > It appears Cygwin setsockopt doesn't do anything with the socket > options SO_RCVTIMEO or SO_SNDTIMEO. Then I also found this: > http://cygwin.com/ml/cygwin/2003-01/msg00833.html > > But those options work on Windows (Win7 to be precise). Has that > always been the case or has Cygwin not caught up yet - IOW, is support > possible/planned? Thanks. I believe there was actually a discussion about this a few weeks back. http://cygwin.com/ml/cygwin/2013-07/msg00112.html Sean -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple