Problem with inn_lock_range

[Alex Kiernan]

Sang-yong Suh <sysuh at kigam.re.kr> writes:

> On Thu, Dec 19, 2002 at 03:57:42AM -0000, Kiernan, Alex wrote:
> > 
> > I've been staring at the buffindexed problems and, at least on Solaris, I
> > think I know why its broken - inn_lock_range doesn't work for files which
> > are mmaped. Basically all the fcntl(F_SETLKW) return EAGAIN, because:
> > 
> > "    The fcntl() function will fail if:
> > 
> >      EAGAIN
> > ...
> >            or the cmd argument
> >            is F_SETLK, F_SETLK64, F_SETLKW, or F_SETLKW64, manda-
> >            tory file/record locking  is  set,  and  the  file  is
> >            currently   being   mapped  to  virtual  memory  using
> >            mmap(2).
> > "
> 
> The situation is same for Linux:
> 
>        EAGAIN   Operation is prohibited because the file has been
>                 memory-mapped by another process.
> 

But again only for mandatory locks from my reading of the source.

-- 
Alex Kiernan, Principal Engineer, Development, THUS plc