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

[Fairlight]

Yo, homey, in case you don' be listenin', Walter Vaughan done said:
> 
>  From KB's comment, I'll take it that to update an index, filePro locks 
> a segment of the index, updates bytes as needed, and closes the lock. 
> Somehow I had in the back of my head that some sort of shared memory 
> structure was involved with indexes.

I'd concur.

> So properly tuned, nfs mounted filePro should work.

Well, v3 anyway.  Anyone know what SCO is using?  

This brings up an interesting question as well--will it work over SMB
mounts?  I saw No Locks Available references relating to samba on SuSE9
during my searches as well, so I'm curious if SMB/CIFS allows for the
required segment locking.

> Okay. I've learned something here. At least I'm not as afraid of nfs as 
> I was before.

A long, long time ago I was frightened of it almost literally.  Someone
made it out as this incredibly hard to administer subsystem.  When I
finally had no choice but to learn it, I about died laughing at the ease of
it all.  Anyone willing and able to take their Slackware 1.0 all the way
through a.out->ELF and then libc5->glibc1 -manually- shouldn't really be
phased by NFS.  A most delicious irony, since I was still shying away from
NFS after all that. 

Last time I listen to anyone when they say a subsystem is difficult.  Well,
I hear news is a PITA to administer "correctly", and maybe it is.  But
people have said that about email as well, and that's not been the case in
many a year.

But NFS itself, I dunno.  Some people cite really poor performance.  I have
to wonder if they bothered tuning it--even moderately tweaking it.  

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!  
Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html