Re: Serious locking problem in CURRENT

[David Malone]

> The lock doesn't seem to be released until *explicitly* released, like
> the manual page says. I don't think closing the descriptor counts as
> an explicit unlock, though I am probably wrong. Run this program,
> you'll see the parent still has the lock. Change close(fd) to flock(fd,
> LOCK_UN) and you'll see it doesn't. It's possible I've misunderstood
> something though.

On -current it seems to be unlocking regardless - which I think it the
problem. If you have to explicitly unlock then that seems fine.

        David.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message