Sponsored Content
Full Discussion: Unix message Queue
Top Forums UNIX for Advanced & Expert Users Unix message Queue Post 38919 by Perderabo on Wednesday 30th of July 2003 11:12:50 AM
Old 07-30-2003
Hmmm....you do have a point. I was getting CBYTES mixed up with QBYTES.

I agree, for the most part, QNUM = 0 and CBYTES != 0 is not consistent. But I can think of one exception where it might make sense. When you do your msgsnd, you are setting msgflg to zero. That means that IPC_NOWAIT is turned off. The msgsnd system call checks to see if this message would exceed some limits. This includes a check of the message queue you are using as well as some system wide limits. If a msgsnd would exceed a limit and it did not set IPC_NOWAIT, the msgsnd system call will suspend until it is safe to send the message. I don't know what state the message queue is in during this suspension. It could well be that CBYTES has been increased but QNUM has not yet been incremented.

This would explain why it works for a few hours and then locks up. Reproduce the error and then run "ipcs -qa" and compare the total messages queue resources in use against your kernel parameters. If this is the problem, you will need to increase the kernel parameters. Or you may have a message queue leak somewhere.

That is my only idea. If it's not that, I would next suspect a broken kernel. You might check for any appropiate patches.
 

10 More Discussions You Might Find Interesting

1. Programming

a message queue question..

Hi there: Thanks first. When I use a message queue amony severl processes, will I have to synchronize the queue? I don't think I would have to because a message queue is implemented in a link listed. Correct me If I am wrong... (0 Replies)
Discussion started by: yanhu
0 Replies

2. Programming

Deleting ALL message queue

hi all, I'm working on this problem for 2 days. Can somebody tell me that how to delete all message queues from the system ? Since "ipcs -q" gives the list of all existing message queue, then there must be a system call and data stucture where from I can fetch the data about all existing... (2 Replies)
Discussion started by: v_rathor
2 Replies

3. Programming

Message Queue Problem Again..

Is there any way one can delete , say , a particular message from a message queue on system V? (2 Replies)
Discussion started by: satansfury
2 Replies

4. IP Networking

message queue problem

I am sending and retriving the message to the queue the problem is after retrieving the message can i see what is there in my message queue. (actually in my application i am encountring some garbage value) so i want to retieve this garbage value and also want to know its size how... (0 Replies)
Discussion started by: ramneek
0 Replies

5. Programming

message queue

Hello, i need to write a message queue "chat server", that should work only localy. Can anyone please help me with some ideas and peshaps code. I'm studying the UNIX IPC mechanisms right now. So far, i understand how it works but i still cannot get an idea how to write a chat programm... ... (2 Replies)
Discussion started by: etenv
2 Replies

6. Programming

How to limit max no of message in a posix message queue

Hii can anyone pls tell how to limit the max no of message in a posix message queue. I have made changes in proc/sys/fs/mqueue/msg_max But still whenever i try to read the value of max. message in the queue using attr.mq_curmsgs (where struct mq_attr attr) its giving the default value as 10.... (0 Replies)
Discussion started by: mohit3884
0 Replies

7. Programming

Message Queue Problem

Hi all, I need help about message queues, i have a server-client program that communicates each other via msg queue, firstly server opens its msg queue and waits for msg then client opens server msg queue and its own msg queue(for receiving msg from server,clients sends msg to server msg... (7 Replies)
Discussion started by: SaTYR
7 Replies

8. Programming

UNIX Message Queue

Hello !!!!! I have a simple question but i can't find the answer anywhere hope to meet it here. Why it is a bad idea to pass pointers through message queues ? Most structs i see all of their char types are arrays... Is it becase having pointers means we could possibily send wrong bytes ? For... (2 Replies)
Discussion started by: qlyine
2 Replies

9. Shell Programming and Scripting

Move xml files from unix to message queue.

Hi, I need to move the XML files from the UNIX to the message queue. Please help me out to write the code.. Thanks, Mohana Krishnan (0 Replies)
Discussion started by: krishnan_6015@y
0 Replies

10. Programming

Please help:program hang stuck there signal handling on POSIX Message Queue UNIX C programming

in a single main() function,so need signal handling. Use Posix Message Queue IPC mechanism , can ignore the priority and other linked list message,to implement the scenario: client:Knock Knock server:who's there client: Eric Server:Eric,Welcome. client:exit all process terminated ... (1 Reply)
Discussion started by: ouou
1 Replies
MSGOP(2)						     Linux Programmer's Manual							  MSGOP(2)

NAME
msgrcv, msgsnd - message operations SYNOPSIS
#include <sys/types.h> #include <sys/ipc.h> #include <sys/msg.h> int msgsnd(int msqid, const void *msgp, size_t msgsz, int msgflg); ssize_t msgrcv(int msqid, void *msgp, size_t msgsz, long msgtyp, int msgflg); DESCRIPTION
The msgsnd() and msgrcv() system calls are used, respectively, to send messages to, and receive messages from, a message queue. The call- ing process must have write permission on the message queue in order to send a message, and read permission to receive a message. The msgp argument is a pointer to caller-defined structure of the following general form: struct msgbuf { long mtype; /* message type, must be > 0 */ char mtext[1]; /* message data */ }; The mtext field is an array (or other structure) whose size is specified by msgsz, a nonnegative integer value. Messages of zero length (i.e., no mtext field) are permitted. The mtype field must have a strictly positive integer value. This value can be used by the receiv- ing process for message selection (see the description of msgrcv() below). msgsnd() The msgsnd() system call appends a copy of the message pointed to by msgp to the message queue whose identifier is specified by msqid. If sufficient space is available in the queue, msgsnd() succeeds immediately. (The queue capacity is defined by the msg_qbytes field in the associated data structure for the message queue. During queue creation this field is initialized to MSGMNB bytes, but this limit can be modified using msgctl(2).) If insufficient space is available in the queue, then the default behavior of msgsnd() is to block until space becomes available. If IPC_NOWAIT is specified in msgflg, then the call instead fails with the error EAGAIN. A blocked msgsnd() call may also fail if: * the queue is removed, in which case the system call fails with errno set to EIDRM; or * a signal is caught, in which case the system call fails with errno set to EINTR;see signal(7). (msgsnd() is never automatically restarted after being interrupted by a signal handler, regardless of the setting of the SA_RESTART flag when establishing a signal han- dler.) Upon successful completion the message queue data structure is updated as follows: msg_lspid is set to the process ID of the calling process. msg_qnum is incremented by 1. msg_stime is set to the current time. msgrcv() The msgrcv() system call removes a message from the queue specified by msqid and places it in the buffer pointed to by msgp. The argument msgsz specifies the maximum size in bytes for the member mtext of the structure pointed to by the msgp argument. If the mes- sage text has length greater than msgsz, then the behavior depends on whether MSG_NOERROR is specified in msgflg. If MSG_NOERROR is speci- fied, then the message text will be truncated (and the truncated part will be lost); if MSG_NOERROR is not specified, then the message isn't removed from the queue and the system call fails returning -1 with errno set to E2BIG. The argument msgtyp specifies the type of message requested as follows: * If msgtyp is 0, then the first message in the queue is read. * If msgtyp is greater than 0, then the first message in the queue of type msgtyp is read, unless MSG_EXCEPT was specified in msgflg, in which case the first message in the queue of type not equal to msgtyp will be read. * If msgtyp is less than 0, then the first message in the queue with the lowest type less than or equal to the absolute value of msgtyp will be read. The msgflg argument is a bit mask constructed by ORing together zero or more of the following flags: IPC_NOWAIT Return immediately if no message of the requested type is in the queue. The system call fails with errno set to ENOMSG. MSG_EXCEPT Used with msgtyp greater than 0 to read the first message in the queue with message type that differs from msgtyp. MSG_NOERROR To truncate the message text if longer than msgsz bytes. If no message of the requested type is available and IPC_NOWAIT isn't specified in msgflg, the calling process is blocked until one of the following conditions occurs: * A message of the desired type is placed in the queue. * The message queue is removed from the system. In this case the system call fails with errno set to EIDRM. * The calling process catches a signal. In this case the system call fails with errno set to EINTR. (msgrcv() is never automatically restarted after being interrupted by a signal handler, regardless of the setting of the SA_RESTART flag when establishing a signal han- dler.) Upon successful completion the message queue data structure is updated as follows: msg_lrpid is set to the process ID of the calling process. msg_qnum is decremented by 1. msg_rtime is set to the current time. RETURN VALUE
On failure both functions return -1 with errno indicating the error, otherwise msgsnd() returns 0 and msgrcv() returns the number of bytes actually copied into the mtext array. ERRORS
When msgsnd() fails, errno will be set to one among the following values: EACCES The calling process does not have write permission on the message queue, and does not have the CAP_IPC_OWNER capability. EAGAIN The message can't be sent due to the msg_qbytes limit for the queue and IPC_NOWAIT was specified in msgflg. EFAULT The address pointed to by msgp isn't accessible. EIDRM The message queue was removed. EINTR Sleeping on a full message queue condition, the process caught a signal. EINVAL Invalid msqid value, or nonpositive mtype value, or invalid msgsz value (less than 0 or greater than the system value MSGMAX). ENOMEM The system does not have enough memory to make a copy of the message pointed to by msgp. When msgrcv() fails, errno will be set to one among the following values: E2BIG The message text length is greater than msgsz and MSG_NOERROR isn't specified in msgflg. EACCES The calling process does not have read permission on the message queue, and does not have the CAP_IPC_OWNER capability. EAGAIN No message was available in the queue and IPC_NOWAIT was specified in msgflg. EFAULT The address pointed to by msgp isn't accessible. EIDRM While the process was sleeping to receive a message, the message queue was removed. EINTR While the process was sleeping to receive a message, the process caught a signal; see signal(7). EINVAL msgqid was invalid, or msgsz was less than 0. ENOMSG IPC_NOWAIT was specified in msgflg and no message of the requested type existed on the message queue. CONFORMING TO
SVr4, POSIX.1-2001. NOTES
The inclusion of <sys/types.h> and <sys/ipc.h> isn't required on Linux or by any version of POSIX. However, some old implementations required the inclusion of these header files, and the SVID also documented their inclusion. Applications intended to be portable to such old systems may need to include these header files. The msgp argument is declared as struct msgbuf * with libc4, libc5, glibc 2.0, glibc 2.1. It is declared as void * with glibc 2.2 and later, as required by SUSv2 and SUSv3. The following limits on message queue resources affect the msgsnd() call: MSGMAX Maximum size for a message text: 8192 bytes (on Linux, this limit can be read and modified via /proc/sys/kernel/msgmax). MSGMNB Default maximum size in bytes of a message queue: 16384 bytes (on Linux, this limit can be read and modified via /proc/sys/ker- nel/msgmnb). The superuser can increase the size of a message queue beyond MSGMNB by a msgctl(2) system call. The implementation has no intrinsic limits for the system wide maximum number of message headers (MSGTQL) and for the system wide maximum size in bytes of the message pool (MSGPOOL). SEE ALSO
msgctl(2), msgget(2), capabilities(7), mq_overview(7), svipc(7) COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2012-05-31 MSGOP(2)
All times are GMT -4. The time now is 08:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy