Date: Thu, 30 Nov 2000 10:14:47 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Peter J. Farley III" <pjfarley AT banet DOT net>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Locking fcntl() and flock() patches
In-Reply-To: <5.0.1.4.0.20001129224255.025ab530@pop5.banet.net>
Message-ID: <Pine.SUN.3.91.1001130101342.23133O@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 29 Nov 2000, Peter J. Farley III wrote:
> <Snipped>
>  >> Well, I think on systems that support large files, type "off_t" is
>  >> probably a "long long", whatever that means on those systems.
>  >
>  >No, I don't think so.  Changing off_t to long long would break lots of
>  >existing code which assumes off_t and ssize_t are compatible.
> 
> Well, if that's the case then I don't know what else to say.  Obviously 
> we *can* widen them, but I don't have the expertise to say if we 
> *should* do so.  What we need here is someone with experience on a 
> system that actually has the capability.

Not necessarily with experience, just with access to that system's man
pages and system headers ;-)

Anyone out there who can tell how does fcntl locking support files larger 
than 2GB on Unix or GNU/Linux systems?