public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: Ray Easton <ray.easton@wcom.com>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: #includes not being processed across network (revised)
Date: Fri, 05 Jan 2001 08:52:00 -0000	[thread overview]
Message-ID: <4.3.1.2.20010105114335.01ddeaf0@pop.ma.ultranet.com> (raw)
In-Reply-To: <3A55F8DD.63728026@wcom.com>

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@rfk.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

  reply	other threads:[~2001-01-05  8:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05  7:20 M4um
2001-01-05  7:41 ` Larry Hall (RFK Partners, Inc)
2001-01-05  8:01   ` Markus Hoenicka
2001-01-05  8:26     ` Larry Hall (RFK Partners, Inc)
2001-01-05  8:42       ` Ray Easton
2001-01-05  8:52         ` Larry Hall (RFK Partners, Inc) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08  8:17 M4um
2001-01-04 12:49 M4um
2001-01-04 12:56 ` Christopher Faylor
2001-01-04  8:24 M4um
2001-01-04  9:38 ` Earnie Boyd
2001-01-04  6:36 M4um
2001-01-04  6:49 ` Earnie Boyd
2001-01-04  5:29 M4um
2001-01-04  6:24 ` Earnie Boyd
2001-01-04  6:27   ` Robert Collins
2001-01-04  6:39     ` Earnie Boyd
2001-01-03 18:35 M4um
2001-01-04  7:40 ` Larry Hall (RFK Partners, Inc)
2001-01-03 18:32 M4um
2001-01-03 13:38 M4um
2001-01-03 14:16 ` Earnie Boyd
2001-01-03 14:40 ` Larry Hall (RFK Partners, Inc)
2001-01-03 11:11 M4um
2001-01-03 11:54 ` Larry Hall (RFK Partners, Inc)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4.3.1.2.20010105114335.01ddeaf0@pop.ma.ultranet.com \
    --to=lhall@rfk.com \
    --cc=cygwin@cygwin.com \
    --cc=ray.easton@wcom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).