Am Montag, 17. Oktober 2005 18:11 hackte Greg Meyer in die Tastatur: > 2) OO.o2 cannot read or write to nfs directories without turning off > file-locking. This seems rather unsafe and maybe something that stops these > packages from making their way into extra for the time being.
I don't know if this error is fixed with the version what i installed now from testing but i haven't this error with "SAL_ENABLE_FILE_LOCKING=1". Perhaps it will be a good idea to compare the differences in our nfs environments. So here are my configurations. The server runs under SuSE 9.3 (kernel 2.6.11) with bind9 running on it and all nfs users are local users in the same group (umask 007) with no shell (/bin/false). The line in the /etc/exports for the the share with the oo files is "/share/work *.localnet(rw,async,root_squash)". The clients runs under arch (what a wonder -)) ) and i mount the shares at bootup. The line in the fstab is: server.localnet:/share/work /mnt/server/work nfs auto,rw,hard,intr,rsize=8192,wsize=8192 0 0 Perhaps we could isolate the error in this way. See you, Attila _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
