Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tiamat!jim
From: jim@tiamat.fsc.com ( IT Manager)
Newsgroups: comp.unix.sysv386
Subject: Re: lockd and informix do not get along
Message-ID: <834@tiamat.fsc.com>
Date: 3 May 91 19:52:15 GMT
References: <1991May2.113913@isdc15.Kodak.COM>
Organization: Ahlstrom Filtration - Chattanooga,TN
Lines: 24

In article <1991May2.113913@isdc15.Kodak.COM>, sengillo@Kodak.COM (Alan Sengillo) writes:
> I have a problem when I run informix on a SCO or Interactive system that is
> running NFS. The problem is that lockd takes up alot of CPU time whenever
> I do a delete from the database. The surpising thing is that the database is
> not on the NFS mount. If I turn NFS off, the problem goes away. Has anyone
> else encountered this problem?

As I understand it, when you use lockd, all system locks are routed through
it. This is so that when a remote system tries to lock a local file,
lockd will know if a local process already has it locked.

If your SCO or Interactive machine is not exporting any thing via NFS
(i.e. you are mounting other system's files to the SCO or ISC box, but
NOT the other way), than you can probably take the lockd stuff out of
your NFS startup file, and not run it.

Also, if you're not exporting anything, and your NFS startup is running
mountd, you can stop those, too, and save a few slots in the process
table.

Good luck.
------------- 
James B. O'Connor			jim@tiamat.fsc.com
Ahlstrom Filtration, Inc.		615/821-4022 x. 651