Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent lock/unlock behaviour on Windows/Linux #6192

Open
p6rt opened this issue Apr 16, 2017 · 1 comment
Open

Inconsistent lock/unlock behaviour on Windows/Linux #6192

p6rt opened this issue Apr 16, 2017 · 1 comment
Labels

Comments

@p6rt
Copy link

p6rt commented Apr 16, 2017

Migrated from rt.perl.org#131158 (status was 'new')

Searchable as RT131158$

@p6rt
Copy link
Author

p6rt commented Apr 16, 2017

From @zoffixznet

On Linux, placing a shared lock on handle opened in write mode (or exclusive on a handle in read mode) throws, while doesn't on Windows.

Also, unlocking a non-locked handle does not throw on Linux, but does throw on Windows.

I think Linux's behaviour is more desirable and Windows's behaviour should be adjusted to match.

I was also given this link, in case it was helpful​: https://github.com/baudehlo/node-fs-ext/blob/master/fs-ext.cc

@p6rt p6rt added the IO label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant