I've been playing around with file locking and Wine, namely the fact that Wine doesn't have any.
Is there any way around this, maybe placing the burden on a filesystem? If I wanted to share files between two different users (say with something dumb like file permissions 666), is there any way to prevent the two people from stomping on each other?
-Brian
Brian Vincent brian.vincent@gmail.com writes:
I've been playing around with file locking and Wine, namely the fact that Wine doesn't have any.
Wine has quite a bit of it actually.
Is there any way around this, maybe placing the burden on a filesystem? If I wanted to share files between two different users (say with something dumb like file permissions 666), is there any way to prevent the two people from stomping on each other?
If you want mandatory locking then yes this has to be done at the filesystem level, by setting the proper mount option and permissions. man fcntl should give you the gritty details.
On 13 Jul 2005 17:18:19 +0200, Alexandre Julliard julliard@winehq.org wrote:
If you want mandatory locking then yes this has to be done at the filesystem level, by setting the proper mount option and permissions. man fcntl should give you the gritty details.
Right.
What I meant was if I'm on Windows and run Word it will warn me if another user already has the file open. It won't let me open it for writing, but I will have the option to open it read only. On Wine it'll just let me open and write to it regardless of what anyone else is doing to the file. Or am I overlooking something?
-Brian
Brian Vincent wrote:
On 13 Jul 2005 17:18:19 +0200, Alexandre Julliard julliard@winehq.org wrote:
If you want mandatory locking then yes this has to be done at the filesystem level, by setting the proper mount option and permissions. man fcntl should give you the gritty details.
Right.
What I meant was if I'm on Windows and run Word it will warn me if another user already has the file open. It won't let me open it for writing, but I will have the option to open it read only. On Wine it'll just let me open and write to it regardless of what anyone else is doing to the file. Or am I overlooking something?
As much of the file locking as possible is done at the file system level, but the only filesystem that supports the Windows style locking semantics is smbfs. The rest we have to emulate in the wineserver. As the wineserver isn't shared between processes (Alexandre is doing work towards making this possible and I am doing work on the security side to make it safe to), the only other alternative is a shared locking server (as suggested by the Samba team). AFAIK, no one has started implementing their suggestion.
Rob
В сообщении от 14 Июль 2005 06:09 Rob Shearman написал(a):
As much of the file locking as possible is done at the file system level, but the only filesystem that supports the Windows style locking semantics is smbfs. The rest we have to emulate in the wineserver. As the wineserver isn't shared between processes (Alexandre is doing work towards making this possible and I am doing work on the security side to make it safe to), the only other alternative is a shared locking server (as suggested by the Samba team). AFAIK, no one has started implementing their suggestion.
Rob, could your explain more in detail, in what condition now work above shared looking server (I correctly understand, what such way of support file loking is now chosen?). I would like, if is possible, participate in its creation, but I do not know, who above what works. For the information on a status of the project as I see it there is a page http://wiki.winehq.org/FileLocking
Vitaly Lipatov wrote:
В сообщении от 14 Июль 2005 06:09 Rob Shearman написал(a):
As much of the file locking as possible is done at the file system level, but the only filesystem that supports the Windows style locking semantics is smbfs. The rest we have to emulate in the wineserver. As the wineserver isn't shared between processes (Alexandre is doing work towards making this possible and I am doing work on the security side to make it safe to), the only other alternative is a shared locking server (as suggested by the Samba team). AFAIK, no one has started implementing their suggestion.
Rob, could your explain more in detail, in what condition now work above shared looking server (I correctly understand, what such way of support file loking is now chosen?). I would like, if is possible, participate in its creation, but I do not know, who above what works. For the information on a status of the project as I see it there is a page http://wiki.winehq.org/FileLocking
I'll add information I know about the problem to the wiki page.
В сообщении от 16 Июль 2005 00:32 Вы написали:
I'll add information I know about the problem to the wiki page.
I guessed it is not needed to communicate between servers... I think user program will calls shared wineserver directly.
I need to get worked shared wineserver ASAP and am ready to do some coding for it. Have you any instructions for me or I need to patching it as I see.
Vitaly Lipatov lav@etersoft.ru writes:
В сообщении от 16 Июль 2005 00:32 Вы написали:
I'll add information I know about the problem to the wiki page.
I guessed it is not needed to communicate between servers... I think user program will calls shared wineserver directly.
I don't think a shared wineserver is the solution. Shared locking has to work on network filesystems too, so it needs to be based on filesystem locking. This is currently implemented for normal locks but not for sharing modes, though that shouldn't be too hard to fix.