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:	Thu, 20 Feb 2003 10:30:11 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: stat/fstat incompatibility w/ unix sockets
Message-ID:	<20030220093011.GA1403@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3E543740 DOT 15115 DOT 880198B AT localhost>
Mime-Version:	1.0
In-Reply-To:	<3E543740.15115.880198B@localhost>
User-Agent:	Mutt/1.4i

On Thu, Feb 20, 2003 at 02:02:40AM -0500, Paul Swartz wrote:
Content-Description: Mail message body
> The man page for stat/fstat says that the results 
> returned should be the same.  However, when asking 
> for the fstat on a unix socket, the result is not 
> the same.  The attached python code demonstrates 
> this problem.  Is this an already known issue with 
> a solution already?  Are there plans to resolve 
> it?

*What* is the difference?  Some details would be helpful.  Especially
I'm not using python at all.  A short test case in C would be appreciated
or at least a description of the difference you see.

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/

- Raw text -