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
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Mon, 14 Apr 2003 19:26:31 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	abraham AT backus DOT com
cc:	cygwin AT cygwin DOT com
Subject:	Re: ENOTSOCK errors with cygwin dll 1.3.21 and 1.3.22
In-Reply-To:	<20030414153815.10292.h012.c000.wm@mail.backus.com.criticalpath.net>
Message-ID:	<Pine.GSO.4.44.0304141917120.26381-100000@slinky.cs.nyu.edu>
Importance:	Normal
MIME-Version:	1.0

On Mon, 14 Apr 2003 abraham AT backus DOT com wrote:

> Hello,
>
> Since 1.3.21 came out, I've had problems with various
> services on my machines (WinXP Home and Win2K).  I use
> inetd to run the UW IMAP server and this has been
> working for a few months now.  When I installed 1.3.21
> (and rebooted) as well as after 1.3.22 came out, I
> started getting syslog messages from imapd "Socket
> operation on non-socket", which is apparently errno of
> ENOTSOCK.  After a little bit of poking around, I found
> that this is after imapd.exe calls gets().
>
> I am also using popfile (http://popfile.sf.net) under
> cygwin, which had been working as well and it doesn't
> even start up now.
>
> I experimented by uncommenting the telnet line in my
> inetd.cnf and I see similar behavior, where my
> connection is dropped immediately after connecting.  I
> even tried switching to xinetd and this behavior still
> occurs.
>
> When I get enough time, I'd like to debug it further
> but I'm hoping that someone on the list might have an
> idea of what changed in 1.3.21 to cause this to happen
> and which code might need to be changed to get
> everything working again.
>
> thanks!
> -Abe

Abe,

Look in winsup/cygwin/ChangeLog between "Bump DLL minor number to 22" and
"Bump DLL minor number to 23"...  You could also look in the cygwin-cvs
list archives between 3/9 and 3/13.

FWIW, I see the following socket-related changes:
<http://cygwin.com/ml/cygwin-cvs/2003-q1/msg00359.html>
<http://cygwin.com/ml/cygwin-cvs/2003-q1/msg00352.html>
<http://cygwin.com/ml/cygwin-cvs/2003-q1/msg00350.html>
but I might have missed something...

Hope this helps,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


--
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/

- Raw text -