02-24-2003
I am guessing that the 2320 is the length of the receive queue. You need to verify that by looking at the heading of the output or your man page. If it is the receive queue, then it indicates something odd. Does it persist? Can you run the command several times and get the same number (or a higher number)? If so, I would suspect that the program who opened that socket is hung or something. I would expect it to pull the udp packets off the receive queue fairly quickly if it was working properly. Packets (ok, datagrams) seem to be arriving at least. It's just that your local program does not seem to be reading them.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Sorry for such a simple question, but being new cannot find any info..
I am trying to ftp a file and checking if the ftp was successful or not. Either way I want to send an e-mail to myself to left me know if good ftp or ftp was not sent. I have the code in the program to do this and am going... (1 Reply)
Discussion started by: roncayenne
1 Replies
2. Programming
is it possible to use a msg queue with multiple threads spawned from the same app? (1 Reply)
Discussion started by: strider
1 Replies
3. Programming
hi...
i posted the code earlier but it wasnt quite readbale... ive added a few comments and made the indentation problem right...
the problem is that it doent seem to be working... ive almost pulled out my hair tryin to fix the prob
another wierd thing is that it worksthe 1st time when i... (0 Replies)
Discussion started by: strider
0 Replies
4. Shell Programming and Scripting
I want to display a message when the script is done running, but I do not want to use echo. Is there another command I can use besides echo? If so, show me how it is done. (1 Reply)
Discussion started by: dshea0001
1 Replies
5. UNIX for Advanced & Expert Users
Can anyone explain?
I start my unix session on AIX, run tcsh move to a particular directory, let say: cd /test/bin and next i run a command like:
grep "test string" /test/bin/*
to look for the string in any files in the directory.
I am getting a response of Killed.
Why is that... (16 Replies)
Discussion started by: gio001
16 Replies
6. UNIX for Dummies Questions & Answers
Is there any way we can view the *.msg files in unix / linux ?
Example cat aa.msg
Or Do we need to do any decryption ?
Kindly provide the solution? (0 Replies)
Discussion started by: kingganesh04
0 Replies
7. Shell Programming and Scripting
Hi,
I have a script to determine the max memory to set a worker to start up at. The variable will need to end up being "-Xmx512m" or "-Xmx256m" or "-Xmx768m."
Everything works fine BUT when I set the "MEMORY" variable I get the "Cmmand not foundine 40: -Xmx512m" msg though the variable is the... (5 Replies)
Discussion started by: vsekvsek
5 Replies
8. AIX
When i run errpt -a, the output was below:
---------------------------------------------------------------------------
LABEL: DMPCHK_NOSPACE
IDENTIFIER: F89FB899
Date/Time: Tue Jan 17 15:00:02 BEIS
Sequence Number: 28998
Machine Id: 0058C0CE4C00
Node Id: ... (2 Replies)
Discussion started by: Ivanku
2 Replies
9. Shell Programming and Scripting
I have a requirement to display a part of an html response that my application gets. The response looks like this:
<html><a href='com.aprisma.spectrum.app.sd.client.SDHyperlinkHandler' sdTicketHandle='cr:419900' ocAlarmId='506618ea-f013-102d-02a7-0050569d7aa8'... (3 Replies)
Discussion started by: dlundwall
3 Replies
10. Solaris
I am new to SOlaris OS, compilation using make files etc.
I have a code base that I am trying to compile under Solaris 2.5 OS. IT has a folder structure, where the root folder contains the master make file which calls each of the make files present in the subfolders to compile the code in... (1 Reply)
Discussion started by: rajujayanthy
1 Replies
LEARN ABOUT OPENSOLARIS
mq_notify
mq_notify(3C) Standard C Library Functions mq_notify(3C)
NAME
mq_notify - notify process (or thread) that a message is available on a queue
SYNOPSIS
#include <mqueue.h>
int mq_notify(mqd_t mqdes, const struct sigevent *notification);
DESCRIPTION
The mq_notify() function provides an asynchronous mechanism for processes to receive notice that messages are available in a message queue,
rather than synchronously blocking (waiting) in mq_receive(3C).
If notification is not NULL, this function registers the calling process to be notified of message arrival at an empty message queue asso-
ciated with the message queue descriptor, mqdes. The notification specified by notification will be sent to the process when the message
queue transitions from empty to non-empty. See signal.h(3HEAD). At any time, only one process may be registered for notification by a spe-
cific message queue. If the calling process or any other process has already registered for notification of message arrival at the speci-
fied message queue, subsequent attempts to register for that message queue will fail.
If notification is NULL and the process is currently registered for notification by the specified message queue, the existing registration
is removed. The message queue is then available for future registration.
When the notification is sent to the registered process, its registration is removed. The message queue is then available for registration.
If a process has registered for notification of message arrival at a message queue and some processes is blocked in mq_receive(3C) waiting
to receive a message when a message arrives at the queue, the arriving message will be received by the appropriate mq_receive(3C), and no
notification will be sent to the registered process. The resulting behavior is as if the message queue remains empty, and this notification
will not be sent until the next arrival of a message at this queue.
Any notification registration is removed if the calling process either closes the message queue or exits.
RETURN VALUES
Upon successful completion, mq_notify() returns 0; otherwise, it returns -1 and sets errno to indicate the error.
ERRORS
The mq_notify() function will fail if:
EBADF The mqdes argument is not a valid message queue descriptor.
EBUSY A process is already registered for notification by the message queue.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
|Standard |See standards(5). |
+-----------------------------+-----------------------------+
SEE ALSO
mq_close(3C), mq_open(3C), mq_receive(3C), mq_send(3C), mqueue.h(3HEAD), siginfo.h(3HEAD), signal.h(3HEAD), attributes(5), standards(5)
SunOS 5.11 5 Feb 2008 mq_notify(3C)