Oplock timing issue.

[David Collier-Brown]

Michael Sweet wrote:
> 
> Jeremy Allison wrote:
> > ...
> > I take it this is on a Linux 2.4 kernel ? The EAGAIN error
> > is not usual for a standard open() call. Can you confirm this
> > please ?
> 
> Both IRIX and Linux (at least) can return EAGAIN on regular files:
> 
>      EAGAIN The file exists, O_CREAT or O_TRUNC are specified,
>             mandatory file/record locking is set, and there are
>             outstanding record locks on the file [see chmod(2)].

	This is a superset of the Posix spec, which only 
	defines: 
	EAGAIN
            The path argument names the slave side  of  a  pseudo-
            terminal device that is locked.
	(stolen from the Solaris man page)

--dave
-- 
David Collier-Brown,           | Always do right. This will gratify 
Performance & Engineering Team | some people and astonish the rest.
Americas Customer Engineering  |                      -- Mark Twain
(905) 415-2849                 | davecb at canada.sun.com