4 ms·
> Every OS that provides exclusive locking, regardless of filesystem, will return an error if more than one process wants to acquire such a lock. Obviously. T
by reitanqild 8y ago
> Every OS that provides exclusive locking, regardless of filesystem, will return an error if more than one process wants to acquire such a lock.
Obviously.
The super annoying thing is when the OS doesn't try to tell you which process(es) keeps it open and doesn't even ship with built in tooling to let you find out on your own.
I think that is the point GP tries to make.
- Negitivefrags 8y agoOpen up "Resource Monitor" and go to the "Disk" tab. Under "Disk Activity" you can see all open file handles.
- coldtea 8y agoWhich are thousands...
- psykotic 8y agoYou need the Sysinternals utilities to make life tolerable: https://docs.microsoft.com/en-us/sysinternals/downloads/handle https://docs.microsoft.com/en-us/sysinternals/downloads/hand... from the command line or Ctrl-F in https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer https://docs.microsoft.com/en-us/sysinternals/downloads/proc... if you prefer a GUI. They do a brute-force search over the open handles in all processes, but it's effective.
- noisem4ker 8y agoI prefer this utility: http://www.emptyloop.com/unlocker/ http://www.emptyloop.com/unlocker/ It lets you see which process locked a file, and optionally remove the lock.
- kevin_thibedeau 8y agoCertainly not a sensible solution like having a dialog button that gives you all the relevant information immediately and empowers you to solve the problem without a goose chase.