Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!usc!apple!agate!ucbvax!ucdavis!csusac!unify!jeff
From: jeff@Unify.Com (Jeff Mischkinsky)
Newsgroups: comp.databases
Subject: Re: Unify - Lockmanager
Message-ID: <8iizdnx@Unify.Com>
Date: 5 Nov 90 16:59:50 GMT
References: <1990Nov3.113849@turtle.Berkeley.EDU> <35571@cup.portal.com> <707@safn2.UUCP>
Organization: Unify Corporation, Sacramento, CA, USA
Lines: 25

In article <707@safn2.UUCP> rey@safn2.UUCP (rey) writes:
>In article <35571@cup.portal.com>, truett@cup.portal.com (Truett Lee Smith) writes:
>> kathy@turtle.Berkeley.edu asks about a message received on a Sun3 when trying
>> to start up Unify.  It says something about being unable to initialize the
>> lock manager.  This usually occurs when trying to run Unify on a machine whose
>> kernel does not have the appropriate IPC (interprocess communication) code
>> included.  The kernel needs to be rebuilt with the IPC code included.  Unify
>> uses IPC to communicate with its lock manager which keeps its data in a shared
>> memory segment.
>
Note: there could be other reasons, such as not enough memory or using
the wrong attach address.  See a previous posting on this subject for
more detailed info.

>Are both semaphores and shared memory necessary, or only shared memory?
>My docs are not consistant on this. I have only shared memory enabled, am
>I loosing some capability?

no, we only use shared memory

-- 
Jeff Mischkinsky		internet: jeff@unify.com
Unify Corporation		          ...!{pyramid,csusac}!unify!jeff
3870 Rosin Court		voice: (916) 920-9092 fax: (916) 921-5340
Sacramento, CA 95834		ICBMS: 38 38 40 N / 120 28 10 W