Sponsored Content
Top Forums Programming message queues and multi-process Post 302134981 by rvan on Wednesday 5th of September 2007 02:06:35 AM
Old 09-05-2007
hi guys,

I was complicating by using mutex which is not needed at all..
as message queue read and write are atomic...

Thanks
 

10 More Discussions You Might Find Interesting

1. Programming

Message queues

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

message queues

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. Linux

maximun number of message queues

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

4. Programming

shared memory and message queues

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

5. UNIX for Advanced & Expert Users

UNIX Message Queues vs. Sockets

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

6. UNIX for Advanced & Expert Users

message queues

#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

7. UNIX for Dummies Questions & Answers

message queues

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

8. Programming

Persisting message queues to disk

Hi, I have searched the forums and could not find a relavant thread discussing my use case, hence the new post. Basically am trying to pass on work to dummy worker instances from controller which will pass on work to workers (client) To make use of host capacity, am planning to serialize... (2 Replies)
Discussion started by: matrixmadhan
2 Replies

9. Shell Programming and Scripting

Cleaning Message Queues

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

10. UNIX for Advanced & Expert Users

Performance calculation for Message Queues

i have a program(C++ Code) that sends/receives information through queue's (Uses MQ) Is there any UNIX/LINUX tool that calculates the load and performance time for the same. If not how do i design the program that calculates the performance time. i know that time.h can be used but it gives... (2 Replies)
Discussion started by: vkca
2 Replies
ptem(7) 						 Miscellaneous Information Manual						   ptem(7)

NAME
ptem - STREAMS pty (pesudo-terminal) Emulation module SYNOPSIS
DESCRIPTION
is a STREAMS module that emulates a terminal when used in conjunction with (STREAMS line discipline) and (STREAMS slave pty driver). The module normally sits above and below The user process must push the module onto the slave side of the pty with a call to the STREAMS ioctl(2) system call before is pushed. is responsible for processing all of the terminal commands that are passed downstream from or from (STREAMS pty master driver). and together provide a real terminal behavior for the STREAMS pty slave. However, some of the terminal commands are ignored and cause only an acknowledgement of the command since there is no real terminal or modem in the pty subsystem. In fact, none of the flags in the field of the or structures, (which is used by the or respectively), have any effect on the pty except if the baud rate is set to zero. Setting the baud rate to zero will have the effect of hanging up the pty connection. Similarly, the parity or delay flags in the field will not have any effect at all on the pty. As a summary, the module performs the following tasks: o The following are processed, if appropriate, and acknowledged by sending an message upstream when they are received on write queue: and o Keeps track of the window size needed for the and o Upon receiving any other on its write queue, acknowledges them negatively by sending an message upstream. o The following are passed downstream by after they have been processed: and o Any message that is received on read queue will be freed in case the module is not pushed on the and the above get to the pty master STREAMS head, which would then send an message downstream. o When is opened and all conditions for setting up a controlling terminal are met, it sends an message (with the flag set) upstream to the STREAMS head to allocate a controlling terminal. o Upon receiving an message of type on its read queue, sends an message downstream and an message upstream. o When an message is received on its write queue to set the baud rate to zero (e.g. with CBAUD set to B0), sends an message upstream and a zero-length message downstream to be read by the pty master process. o When an message of type is received on its read queue, sends an message downstream and an message upstream with the signal number set to the same value used in the message. o When an message of type is received on its read queue, sends an message downstream and an message (with ioc_cmd set to or upstream to enable or disable the input processing on o When an message is received on its read or write queue, simply discards the message without any action. o When an message of type is received on its write queue and if the values in the structure in are not zero, sends an message upstream with the structure. If the values are zero, sends an message upstream. o When an message of type is received on its write queue and if the values in the structure in are not zero, sends an message upstream with the structure. If the values are zero, sends an message upstream. o When an message of type is received in its write queue, saves the information passed to it in the structure and sends an (with the signal number set to upstream to the pty slave process if the window size is changed. o When an message of type is received on its read queue and if the values in the structure in are not zero, sends an message down- stream with the structure. If the values are zero, sends an message downstream. o When an message of type is received in its read queue, saves the information passed to it in the structure and sends an (with the signal number is set to upstream to the pty slave process if the window size is changed. o All other messages not mentioned above are passed to the next module or driver. AUTHOR
was developed by HP. SEE ALSO
ioctl(2), streamio(7), ptm(7), pts(7), ldterm(7). ptem(7)
All times are GMT -4. The time now is 04:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy