From: Martin Stromberg <eplmst AT lu DOT erisoft DOT se>
Message-Id: <200012011435.PAA09759@lws256.lu.erisoft.se>
Subject: Re: Locking fcntl() and flock() patches
To: djgpp-workers AT delorie DOT com
Date: Fri, 1 Dec 2000 15:35:13 +0100 (MET)
In-Reply-To: <Pine.SUN.3.91.1001130101342.23133O@is> from "Eli Zaretskii" at Nov 30, 2000 10:14:47 AM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

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

On Solaris, an except of the man page of fcntl:
     The following commands are  available  for  advisory  record
     locking.  Record locking is supported for regular files, and
     may be supported for other files.

     F_GETLK        Get the first  lock  which  blocks  the  lock
                    description pointed to by the third argument,
                    arg, taken as a pointer to type struct flock,
                    defined   in   <fcntl.h>.    The  information
                    retrieved overwrites the  information  passed
                    to  fcntl()  in  the  structure flock.  If no
                    lock is found that would  prevent  this  lock
                    from  being  created, then the structure will
                    be left unchanged except for  the  lock  type
                    which will be set to F_UNLCK.

     F_GETLK64      Equivalent to F_GETLK,  but  takes  a  struct
                    flock64  argument  rather than a struct flock
                    argument.

Likewise for F_SETLK and F_SETLKW.


Right,

						MartinS