-
Notifications
You must be signed in to change notification settings - Fork 560
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
Win32: stat/unlink fails on UNIX sockets #20204
Comments
Using fsutil:
Possibly relevant: https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/c8e77b37-3909-4fe6-a4ea-2b9d423b1ee4
Looking at that doc there might be some other ones for which something needs to be done in
|
A quick & dirty patch to add some debugging info:
Running:
A quick & dirty fix (on top of the quick & dirty debug patch):
Running:
=> The stat and unlink succeeded. Some more relevant information: https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilea
What I don't know if this makes sense/is good enough.. Relevant part of the Remarks section: https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilea#symbolic-link-behavior |
The main difficulty I see is with symlinks - opening with |
What about first doing a stat without
Also: what about the (perl) |
I have some work in progress code, just still working on it |
I don't think we can avoid the race, luckily it's only an issue for symlink chains to other reparse points.
That's what I'm doing.
All of stat(), lstat() and unlink() have special implementations in |
dist/IO/t/io_unix.t
contains a test that creates a UNIX socket, does some tests and then attempts tounlink
the file.That
unlink
call fails and that results in a stray tmp file.A reduced example case:
Running on Windows 10:
See @tonycoz comment: #20179 (comment)
Other references:
The text was updated successfully, but these errors were encountered: