Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!hao!gatech!uflorida!codas!pdn!tsc3b21!crash
From: crash@tsc3b21.UUCP (Frank "crash" Edwards)
Newsgroups: comp.databases
Subject: Re: UNIFY lockrec
Message-ID: <253@tsc3b21.UUCP>
Date: 14 Mar 88 13:00:33 GMT
References: <316@fairlight.oz>
Organization: Transportation Systems Consulting, Inc, Palm Harbor FL
Lines: 25

From article <316@fairlight.oz>, by gary@fairlight.oz (Gary Evesson):
> For all those UNIFY 3.2 people out there.....
> 
> Has anyone ever had a problem with lockrec never returning if a record is
> locked by another process? If so, how did you get around it? I would love
> to know because it is driving me crazy killing off hung processes.
> 
> 				gary@fairlight.oz
> 				munnari!fairlight.oz!gary@uunet.UU.NET
> 				Gary Evesson.

Sorry Gary, we haven't had that problem.  Actually, I'm not that sorry ;-).

What system are you running Unify on?  We ran for about a year and a half on
an old Momentum box (68000) with Ver7 UNIX with no problems.  And after that,
about 2 years on an AT&T 3B2/310.  Again, with no problems.  The Unify
documentation says that the implmentation of the locking mechanism is system
dependent based on what services are intrinsic to the OS.

Frank (crash) Edwards		...!codas!usfvax2!{pdn,jc3b21}!tsc3b21!crash
TSC in Palm Harbor, FL		Phone:  (813) 785-0583  (voice)
The Sweat Shop			These opinions belong to no one.
-----
"This message brought to you by ...
Bang-Bang!  Makers of the sweetest little automatic in the world!"
                   Radio commercial on Star Trek:  "A Piece of the Action"