filePro on SuSe 9.0 Linux NFS mounts - problem with NO LOCKS AVAILABLE

[Walter Vaughan]

Nancy Palmquist wrote:

> I sent this to fpTech but thought maybe someone on the list could help.

> If I try to add an index to the file, I get a NO LOCKS AVAILABLE system 
> error from filepro.

> Is there a way to configure the system with more locks?  Is this a 
> filePro issue?

A quick google brings up a billion problems with "NO LOCKS AVAILABLE" on 
Suse.

This did seem interesting...

The problem is not exactly SuSE. It's more a combination of which NFS 
server you choose to run (userspace vs. kernel) and making sure lockd 
and statd are running on both the client and the server.

With the SuSE distribution there are two different (conflicting) NFS 
rpms available to install:  nfs-server-XXX.rpm (which contains the 
userspace NFS server), and the nfs-utils-XXX.rpm (which contains the 
kernel NFS server). Locking is not available in the userspace NFS 
server, so you need to uninstall nfs-server-XXX.rpm and install 
nfs-utils-XXX.rpm instead.

Also check "testlk" for proper operation on the client side...

--
Walter "who couldn't find nfs problems on FreeBSD"