4 ms·
My biggest pet Peeve about Windows is the way it accesses files I'm not sure if this is a kernel or filesystem issue. But when a remote user has a file open as
by bigger_cheese 10y ago
My biggest pet Peeve about Windows is the way it accesses files I'm not sure if this is a kernel or filesystem issue. But when a remote user has a file open as long as that file is open other users are prevented from updating or replacing the file. It happens all the time at my work and I know of no obvious way to work out who has the file open because as far as I can tell nothing like lsof exists.
This is probably the number one cause of me banging my head against the desk and wishing Windows behaved more like Linux.
- asveikau 10y agoWhat you can do while it's open is partially defined by the dwShareMode parameter in CreateFile. Unfortunately a lot of people look at the daunting documentation, shrug, and put 0 there, which is the least permissive mode. A lot of libraries do that too. OTOH there are other limits that are not dictated by dwShareMode. Such as deleting files while handles are open - this blocks a new file with the same name from being created until all handles are closed. That's probably the worst one. There are some other crappy ones involving directory handles that I don't care to enumerate.
- pjmlp 10y agoSane OSes don't let people modify files without permission from other users. Windows isn't the only OS having file locking implemented at kernel level.
- JdeBP 10y ago> I'm not sure if this is a kernel or filesystem issue. It's neither. It's a common misconception. See https://news.ycombinator.com/item?id=11415366 https://news.ycombinator.com/item?id=11415366 .