How to set IPC limits in Solaris 2.51
Posted on 1997-09-07
I've got a little program that is trying to add (about) 1000 messages to
an IPC message
queue that it has created. I've set the following system parameters in
2.51 in /etc/system to:
set msgsys:msginfo_msgtql = 65560
set msgsys:msginfo_msgmnb = 1024000
This should set the maximum number of messages in any queue to be 65K,
and the total
number of bytes for a message queue to 1M.
The program is running on an Ultra 1 with 128 meg of memory, and the
system is not taxed.
The program is to add a finite number of messages to the queue, and a
is to later read the messages from the queue.
I am able to create ONLY 341 messages before I get the error EAGAIN
(errno == 11),
and strerror() prints the text: "Resource temporarily unavailable". I
limit at 341
regardless of whether IPC_NOWAIT is set in the flags or not.
I have changed the msgtql from 65560 to 512, and I can still add only
before croaking. Does anyone know what's going on here?
One other simple question: Do Solaris Message Queues have built-in
(unlike Shared Memory where you have to roll your own semaphores)?
That is to say,
can multiple processes add to and remove from a particular Message Queue
having to implement a semaphore?
Any help would be most gratefully appreciated. Please respond to the
news group or to: email@example.com.
What I'm trying to do is to obtain timing information from a
system. I want to track a number (say, 1000) of transactions through
in the system. Each application type will create a message recording
the transaction type, their application type, and the time that the
acted upon by the application. Each of these "timings" are then to be
the message queue. For 1000 records, the message queue needs to be able
to hold about
5000 21-byte messages. We are using a message queue because we want to
to "live" store a number of "timing records" with as little trouble and
Heisenberg) as possible. Once all the transactions have been processed,
want to dump the message queue out via a reader and analyze the timings.
If you have any suggestions as to how this can be better done by
than message queues, please let me know. I'm using message queues
they have IPC, a record-based structure capable of storing more than one
message/record easily, and because I think it has built-in semaphore
Please advise if there are caveats to that last assumption.