Problems with file locking (Ultrix and HP-UX)
George Robbins
grr at cbmvax.commodore.com
Tue Jul 10 07:36:43 AEST 1990
In article <58061 at bbn.BBN.COM> fkittred at spca.bbn.com (Fletcher Kittredge) writes:
>
> I have been testing Posix style file locking on Ultrix 4.0(FT 2)
> and 3.1 on both RISC and VAX in preparation for using it in a
> product. I have had strange results. And was hoping someone could
> enlighten me.
>
> However, on Ultrix 3.1 systems, locking a NFS mounted file is extremely
> slow (200 times slower than locking a local file). This seems to be
> the case whether the Ultrix 3.1 system is the locking client or the
> NFS server. I tested this with the following systems being both
> client and server:
There is a patch against the base 3.1 release having to do with NFS
file locking. I know it applies to the VAX release, but is included in
the latter RISC child releases. Check with the support center...
lockd, klm_lockmgr.o
--------------------
On systems using nfs locking, this daemon and kernel patch will cause
the locks to perform at a much faster rate. In addition, there is a
bug fix or two included.
> In addition, when Ultrix 4.0(FT 2) is the client platform, and HP-UX is
> the server platform, I am unable to get a lock at all. Calling fnctl()
> to lock the first time returns -1 and perror() prints the following
> message on Ultrix:
>
> 2) Is the problem with locking between Ultrix 4.0 and HP-UX a known
> problem, whose problem is it, and when will it be fixed? (I am
> reporting it to Ultrix Field Test).
I think that reporting it as a field test problem would have to be the
starting point - that's what field test releases are for...
--
George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing: domain: grr at cbmvax.commodore.com
Commodore, Engineering Department phone: 215-431-9349 (only by moonlite)
More information about the Comp.unix.ultrix
mailing list