Date: Mon, 26 Jun 2006 07:36:05 +1000 From: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> To: Bruce Evans <bde@zeta.org.au> Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>, freebsd-arch@FreeBSD.org Subject: Re: What's up with our stdout? Message-ID: <20060625213605.GA93766@duncan.reilly.home> In-Reply-To: <20060626002658.A65226@delplex.bde.org> References: <20060625011746.GC81052@duncan.reilly.home> <20060625013110.GA62237@troutmask.apl.washington.edu> <20060625020154.GA89358@gurney.reilly.home> <20060626002658.A65226@delplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 26, 2006 at 01:10:38AM +1000, Bruce Evans wrote:
> This doesn't seem to have anything to do with stdout. F_SETLKW just
> seems to be broken on all regular files (and thus is unsupported for
> all file types). The above works under the modified version of
> FreeBSD-5.2 that I use, but it fails with the documented errno EOPNOTSUPP
> under at least FreeBSD-6.0-STABLE. Replacing STDOUT_FILENO by fd =
> open("foo", O_RDWR) gives the same failure. Replacing FSETLKW by
> FSETLK or F_GETLK gives the same failure.
Thanks for the clarification.
Don't all of the databases rely on fcntl locks? How can this be
broken?
Cheers,
--
Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060625213605.GA93766>