cfinch Newbie

Joined: 09 Aug 2007 Posts: 1
|
Posted: Thu Aug 09, 2007 6:24 am Post subject: File locking in NFS |
|
|
I have searched through the posts and found that this is common issue for people running OO out of an NFS share or that have their home directories mounted on an NFS share. I am currently experiencing a problem where my first attempt to open OO works fine but subsequent attempts hang. After extensive troubleshooting I've narrowed the problem down to file locking in NFS. Specifically the problem appears to be with OO not releasing locks on files.
I'm running OO 2.0 on Solaris 8. Upgrading to a newer version of OO is not an option. I have lockd, statd, and nfsd running. Everything appears to be setup correctly on the Solaris side to support file locking over NFS. Instead of dealing with the NFS issues I decided to disable file locking by editing the /base_dir/program/soffice script. The file locking paramaters have been set in the script as follows.
STAR_PROFILE_LOCKING_DISABLED=1
export STAR_PROFILE_LOCKING_DISABLED
#SAL_ENABLE_FILE_LOCKING=1
#export SAL_ENABLE_FILE_LOCKING
unset SAL_ENABLE_FILE_LOCKING
I've compared a truss output generated prior to making these changes with one that I generated after making the changes and although most of the file locking attempts are gone there are still several left over. The following lines are the actual F_SETLK attempts from the truss output that are still occuring after the changes I made above.
1)
open ("/opt/openoffice.org2.0/program/types.rdb", O_RDONLY) = 8
fnctl (8, F_SETLK, 0xFFBEE480)
2)
open ("/opt/openoffice.org2.0/program/services.rdb", O_RDONLY) = 9
fnctl (9, F_SETLK, 0xFFBEE480)
3)
open ("/export/home/adminusr/.recently-used", O_RDWR) = 24
fnctl (24, F_SETLKW, 0xFFBECCCC)
After disabling the locking I'm able to get a bit farther when launching OO. Whereas the app would hang during launch it now opens to a viewer and then hangs. Unless I'm missing something it appears that the ability to disable file locking through the soffice script doesn't really work 100%.
Any help would be appreciated,
Thanks,
Chris |
|