Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.3.1.2.20010105114335.01ddeaf0@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 05 Jan 2001 11:48:39 -0500 To: Ray Easton , "cygwin AT cygwin DOT com" From: "Larry Hall (RFK Partners, Inc)" Subject: Re: #includes not being processed across network (revised) In-Reply-To: <3A55F8DD.63728026@wcom.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:39 AM 1/5/2001, Ray Easton wrote: >"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. No argument here with regards to the quick solution proposed. It appears that Samba functions quite nicely so I expect converting to use that as the file server is a quicker solution (with a more time-tested outcome). Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple