Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!usc!csun!csusac!unify!bab
From: bab@unify.UUCP (Bob Batchelder)
Newsgroups: comp.databases
Subject: Re: Use of Sys V IPC features by RTI Ingres
Message-ID: <887@unify.UUCP>
Date: 30 Jun 89 16:58:15 GMT
References: <386@odi.ODI.COM>
Reply-To: bab@unify.UUCP (Bob Batchelder)
Organization: Unify Corporation, Sacramento, CA, USA
Lines: 30

In article <386@odi.ODI.COM> dlw@odi.com writes:
>A few weeks ago, I believe someone mentioned that the new version of
>RTI's Ingres makes use of one of the System V IPC features (shared
....
>kernel distributed by Sun Microsystems, the System V IPC features
>are not assembled in; if you want them, you have to build a kernel
....
>kernels and who have permission to do so.  In actual practice, would
>anyone expect this to be a problem, or is it unlikely to ever cause
>problems?
....

Well, your correct, not all kernels are sent configured for SYS V
IPC features.  Some which are, do not expect a "large" configuration
to be required.  Shared memory segment may be limited to a small
size.

We use shared memory with our products and so we have provided machine 
specific notes for those machines which need to be reconfigured to work 
well.  In some instances, we have sent the user to the hardware vendor 
for help.  The results, which I am sure RTI will find, have been quite good.  
The UNIX customer seems to be hardened to unexpected extras. ;-)

I would not expect this to cause problems for them.  The benefits
of using the SYS V features will far outweigh the slight inconvenience
for any of their customers.

Bob Batchelder     
Quality Assurance  (Where a quality time is assured.)
Unify Corp.