Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Fri, 05 Jan 2001 10:39:58 -0600
From: Ray Easton <ray DOT easton AT wcom DOT com>
Subject: Re: #includes not being processed across network (revised)
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Message-id: <3A55F8DD.63728026@wcom.com>
MIME-version: 1.0
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
References: <4 DOT 3 DOT 1 DOT 2 DOT 20010105103456 DOT 01e04db8 AT pop DOT ma DOT ultranet DOT com>
 <6f DOT f5ad834 DOT 27874020 AT aol DOT com>
 <4 DOT 3 DOT 1 DOT 2 DOT 20010105103456 DOT 01e04db8 AT pop DOT ma DOT ultranet DOT com>
 <4 DOT 3 DOT 1 DOT 2 DOT 20010105110638 DOT 01db7568 AT pop DOT ma DOT ultranet DOT com>

"Larry Hall (RFK Partners, Inc)" wrote:

> Thanks Markus, this information is quite helpful.  Since there isn't an issue
> with Samba, the Win32 APIs being used in Cygwin are clearly sufficient to
> provide the information required (i.e. file sizes in this case) in a network
> environment in general.  However, in this particular case in this particular
> network environment, there may be an issue.  I would guess that there is
> either a problem with permissions (which John has stated that he's looked at
> before) or there is some other Win32 API that provides the file size even with
> John's setup (which the DOS tools use and Cygwin does not).  What is clear to
> me by all this is that the quickest way to resolve this issue is to debug the
> code, for better or worse...
>
> Larry

I've seen fstat() returning zero problems many times in many contexts (though *not*
with cygwin) and in each case it has been due to bugs in the file server software --
in which case debugging cygwin code will be useless.  The quickest way to resolve the
issue is more likely simply to replace the file server software.

--

ray

    -- je suis marxiste, tendance groucho



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple