Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Fri, 28 Feb 2003 17:07:38 -0500 From: Jason Tishler Subject: Re: 1.3.21 In-reply-to: <20030221153741.GA26756@redhat.com> To: cygwin-developers AT cygwin DOT com Mail-followup-to: cygwin-developers AT cygwin DOT com Message-id: <20030228220716.GA1244@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4i References: <20030221153741 DOT GA26756 AT redhat DOT com> On Fri, Feb 21, 2003 at 10:37:41AM -0500, Christopher Faylor wrote: > Is there anything wonderful waiting in the wings? Sorry for YA, um, maybe... I'm seeing stat related problems with sockets in the latest snapshot, 2003-Feb-25: 1. exim is reporting the following: 2003-02-28 16:05:34 daemon: fclose(smtp_in) failed: Socket operation on non-socket 2. vsftpd is not starting up because the following code snippet: vsf_sysutil_fstat(VSFTP_COMMAND_FD, &p_statbuf); if (!vsf_sysutil_statbuf_is_socket(p_statbuf)) { die("vsftpd: does not run standalone, must be started from inetd"); } ... int vsf_sysutil_statbuf_is_socket(const struct vsf_sysutil_statbuf* p_stat) { const struct stat* p_realstat = (const struct stat*) p_stat; return S_ISSOCK(p_realstat->st_mode); } Note that CVS from 2003-02-20 does not exhibit the above problems. This is just a heads up post -- I will dig (much) deeper, but most likely not until Monday. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6