Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ncar!ico!onecom!baldur.uucp!john
From: john@baldur.uucp (John Brinegar)
Newsgroups: comp.unix.sysv386
Subject: Message queues
Message-ID: <1990Dec14.184004.2222@onecom>
Date: 14 Dec 90 18:40:04 GMT
Sender: john@onecom (John Brinegar)
Organization: TelWatch Inc., 2905 Wilderness Place, Boulder, CO 80301
Lines: 33

Following is an request I am posting for a friend that doesn't have net
access.  Please respond to the voice phone number given at the end of the
article.
---------------------------------------------------------------------------

I am wondering if anyone has source to help me with a problem I have
encountered in a project I am working on.  I am using
System V (Venix) and need more messages outstanding in the
message queues than apparently the system will alow.
According to what I decypher from mtune, I can only have
40 messages outstanding systemwide.  But the biggest limitation
is the 128K limitation due to the way message queues are
implemented.
Essentially, my requirements are as follows:

Message length max = 512 (may get by with 256 bytes)
40 queues
Max # of outstanding messages = 500
Different queues may have different max message lengths.
The messages need to be accessed randomly. (Not FIFO)

What I am hoping for is that someone has developed the code
implementing message queues in shared memory.


I can be reached at (daytime, voice)
phone # (303) 939-6922  Robert Payne

---------------------------------------------------------------------------

-- 
John D. Brinegar	{att!uswat, uunet!dunike} !onecom!john
TelWatch Inc.  		(303) 440-4756