Hi-- The problem: Two users can have the same OOo file open at the same time, and both edit it. The last one to save the file wins! The system: 3 Ubuntu 5.10 client boxes and one WinXPPro client box, all running OOo 2.0; one server with RedHat 9.0 running samba version 2.2.7a-security-rollup-fix. Did some further testing and found that I could gedit a file at the same time on both computers, too. Trying to vi the same file on both produced an error in vi, either at the opening of the file or at the saving. But KWord could have a file open and edit it when it was open and being edited in gedit. This suggests to me that it is not wholly an OOo issue, although OOo might have an internal solution. I tried this, hoping it would be solved by OOo-- export SAL_ENABLE_FILE_LOCKING=1 but it made no difference. Even did another one changing STAR for SAL, and no difference either. When we had all Win95 boxes as clients, our files did seem to lock properly. (We used Ami Pro 3.1 for word processing, Lotus 1-2-3 for spreadsheets). So, got any ideas how to trouble shoot this? Thanks! :- Doug.
> The problem: Two users can have the same OOo file open at the same time, and > both edit it. The last one to save the file wins! > The system: 3 Ubuntu 5.10 client boxes and one WinXPPro client box, all running > OOo 2.0; one server with RedHat 9.0 running samba version > 2.2.7a-security-rollup-fix.I doubt this has anything to do with Samba. If you want to have proper file locking you need to actually mount the CIFS filesystem; otherwise you are most likely opening and saving the file via GNOME-VFS (ldd /usr/lib/ooo-2.0/program/ucpgvfs1.uno.so | grep -i vfs). If your using GNOME-VFS it works by getting the file to a temporary local file and when you save it puts the file back to the server, like and FTP GET/PUT; therefore there is no file lock and the last writer wins.
Adam-- You are a wonder worker! I entered your command and the response I got was-- libgnomevfs-2.so.0 => /usr/lib/libgnomevfs-2.so.0 (0xb7b53000) which I suspect is pretty much what you expected. Right? In any case, after reading HOWTOs and man files and README files I edited /etc/fstab and changed the instances of smbfs to cifs. It mounted right away, and the files now lock linux to linux and linux to winXP Pro. (At least for OOo. KWord does not respect the locks, nor does gedit. I suspect that will not be a problem, but I wonder why not?) Thank you, thank you, thank you! Adam you have rescued me from having spent 2 1/2 weeks of work till midnight trying to get some file locking going! You are a wonder, Adam! :- Doug.