04-04-2012
10 More Discussions You Might Find Interesting
1. Programming
Hi all,
I've been trying for hours to figure out how to turn my 2-program (one to send and one to receive) "chat system" using message queues, into a single program where each concurrent component (entity) will both send and receive messages. PLEASE give me a hand with this, I'm starting to... (9 Replies)
Discussion started by: mgchato
9 Replies
2. UNIX for Dummies Questions & Answers
let 3 processes a, b and c are sharing msgs using msg queues.process 'a' sending msg to 'c' and in turn 'c' send sthat msg to 'b'.if something happens to c how can 'a' and 'b' know that 'c' is not available?????? (2 Replies)
Discussion started by: sukaam
2 Replies
3. Solaris
We have message queues created from our ERP system to our tax system via an application api written by the ERP software vendor.
Occasionally when a user does not gracefully exit the ERP application, the message queue hangs. After a few months, this becomes a problem as the queues are all used... (2 Replies)
Discussion started by: MizzGail
2 Replies
4. Linux
how to check the maximun number of message queues in current linux enviornment? is there any command ? (4 Replies)
Discussion started by: princelinux
4 Replies
5. Programming
Hi,
According to my understanding..
When message queues are used, when a process post a message in the queue and if another process reads it from the queue then the queue will be empty unlike shared memory where n number of processess can access the shared memory and still the contents remain... (2 Replies)
Discussion started by: rvan
2 Replies
6. UNIX for Advanced & Expert Users
If I use sockets for IPC, and can easily distribute my applications.
UNIX Message Queues are local to the processor.
As I understand it, Message Queues still incur system call overhead, just like socket calls.
What advantage does a UNIX Message Queue provide versus a TCP or UDP Socket,... (2 Replies)
Discussion started by: zen29sky
2 Replies
7. Programming
Hi,
Am supposed to use message queues to send and receive messages between the processes. when i was working on that i realised that the message qid and the message queue related data should be maintained in a shared memory so that it can be accessed by all the processes. Could anybody refer... (10 Replies)
Discussion started by: rvan
10 Replies
8. UNIX for Advanced & Expert Users
#include <sys/ipc.h>
#include <sys/msg.h>
int main()
{
int qid;
int t;
struct msgbuf mesg;
qid=msgget(IPC_PRIVATE,IPC_CREAT);
mesg.mtype=1L;
mesg.mtext=1;
t=msgsnd(qid,&mesg,1,0);
printf("%d",t);
}
the program prints -1 as the result of msgsnd ,which means that msgsnd doesn't... (1 Reply)
Discussion started by: tolkki
1 Replies
9. UNIX for Dummies Questions & Answers
can any body provide a tutorial that explains the concept of message queues in UNIX in great detail (1 Reply)
Discussion started by: asalman.qazi
1 Replies
10. Shell Programming and Scripting
i have an application installed on AIX 5.3 and i have made a script that shutdown a proccesses that exceeded 10000kb of memory usage but i have a problem with cleaning the message queues of these proccesses after shutting them down. Is there any way to clean the message queues for this particular... (8 Replies)
Discussion started by: Portabello
8 Replies
rwhod(1M) rwhod(1M)
NAME
rwhod - system status server
SYNOPSIS
DESCRIPTION
is the server that maintains the database used by and (see rwho(1) and ruptime(1)). sends status information to and receives status infor-
mation from other nodes on the local network that are running
is started at system boot time if the RWHOD variable is set to 1 in the file
As an information sender, it periodically queries the state of the system and constructs status messages that are broadcast on a network.
As an information receiver, it listens for other servers' status messages, validates them, then records them in a collection of files
located in the directory.
By default, both sends and receives information. also supports the following options:
Configures server to be an information sender only.
Configures server to be an information receiver only.
Status messages are generated approximately once every three minutes. transmits and receives messages at the port indicated in the service
specification (see services(4)). The messages sent and received, are of the form:
All fields are converted to network byte order before transmission. System load averages are calculated from the number of jobs in the run
queue over the last 1-, 5- and 15-minute intervals. The host name included is the one returned by the system call (see gethostname(2)).
The array at the end of the message contains information about the users logged in on the sending machine. This information includes the
contents of the entry for each non-idle terminal line and a value indicating the time since a character was last received on the terminal
line (see utmp(4)).
discards received messages if they did originate at a server's port, or if the host's name, as specified in the message, contains any
unprintable ASCII characters.
Valid messages received by are placed in files named in the directory. These files contain only the most recent message in the format
described above.
WARNINGS
does not relay status information between networks. Users often incorrectly interpret the server dying as a machine going down.
AUTHOR
was developed by the University of California, Berkeley.
FILES
Information about other machines.
SEE ALSO
rwho(1), ruptime(1), gethostname(2), services(4), utmp(4).
rwhod(1M)