Sponsored Content
Full Discussion: Cleaning Message Queues
Top Forums Shell Programming and Scripting Cleaning Message Queues Post 302529498 by Portabello on Thursday 9th of June 2011 12:01:19 PM
Old 06-09-2011
Quote:
Originally Posted by Corona688
How are you killing this process? It's possible that if you let it shutdown cleanly it may delete them itself.
buy kill command

well it doesn't and the message queues still exist even after shutting the processes down
 

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

rogue message queues solaris 9

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

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

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

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

7. Programming

message queues and multi-process

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

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

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

10. 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
ipcs(1) 						      General Commands Manual							   ipcs(1)

NAME
ipcs - Reports Interprocess Communication (IPC) facility status SYNOPSIS
ipcs [-a | -bcopt] [-mqs] [-C corefile] [-N namelist] The ipcs command writes to the standard output information about active Interprocess Communication (IPC) facilities. STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: ipcs: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Same as specifying the -b, -c, -o, -p, and -t options. Writes the maximum number of bytes in message queues, the size of segments for shared memory, and the number of semaphores in each semaphore set. Writes the username and group name of the user that made the facility. Writes report based on contents of file corefile instead of /dev/kmem. Writes information about active shared memory segments. Writes report based on contents of file namelist instead of /vmunix. Writes the following usage information: Number of messages on queue Total number of bytes in message queues Number of processes attached to shared memory segments Writes the following: Process number of the last process to receive a message on message queues Process number of the creating process Process number of last process to attach or detach on shared memory segments Writes information about active message queues. Writes information about active semaphore set. Writes the follow- ing: Time of the last control operation that changed the access permissions for all facilities Time of the last msgsnd() and last msgrcv() on message queues Time of the last shmat() and last shmdt() on shared memory Time of the last semop() on semaphore sets DESCRIPTION
If you do not specify any options, ipcs writes information in a short form about currently active message queues, shared memory segments, semaphores, remote queues, and local queue headers. Column Headings The column headings and the meaning of the columns in an ipcs listing follow. The letters in parentheses indicate the flags that cause the corresponding heading to appear. The word all means that the heading always appears. The flags only determine what information is pro- vided for each facility; they do not determine which facilities are listed. Type of facility: Message queue Shared memory segment Sema- phore The identifier for the facility entry. The key used as a parameter to the msgget(), semget() or shemget() system calls to make the facility entry. Note that the key of a shared memory segment is changed to IPC_PRIVATE when the segment is removed. This change remains in effect until all processes attached to the segment detach it. The facility access modes and flags. The mode consists of 11 characters that are interpreted as follows: The first two characters can be: [Tru64 UNIX] If the associated shared memory segment was locked. If a process is waiting on a msgrcv() system call. If a process is waiting on a msgsnd() system call. If the associated shared memory segment was removed. It disappears when the last process attached to the segment detaches it. If the corresponding special flag is not set. The next nine characters are interpreted as three sets of three bits each. The first set refers to the owner's permissions, the next to permissions of others in the user group of the facility entry, and the last to all others. Within each set, the first char- acter indicates permission to read, the second character indicates permission to write or alter the facility entry, and the last character is currently unused. The permissions are indicated as follows: Read permission is granted. Write permission is granted. Alter permission is granted. The indicated permission is not granted. The username of the owner of the facility entry. The name of the group that owns the facility entry. The username of the creator of the facility entry. The group name of the group of the creator of the facility entry. Note that for the OWNER, GROUP, CREATOR, and CGROUP, the user and group IDs display instead of the usernames. The number of bytes in messages currently outstanding on the associated message queue. The number of messages currently outstanding on the associated message queue. The maximum number of bytes allowed in messages outstanding on the associated message queue. The ID of the last process that sent a message to the associated queue. The ID of the last process that received a message from the associated queue. The time when the last message was sent to the associated queue. The time when the last message was received from the associated queue. The time when the associated entry was created or changed. The number of processes attached to the associated shared memory segment. The size of the associated shared memory segment. The process ID of the creator of the shared memory entry. The process ID of the last process to attach or detach the shared memory segment. The time when the last attach was completed to the associated shared memory segment. The time when the last detach was completed on the associated shared memory segment. The number of sema- phores in the set associated with the semaphore entry. The time when the last semaphore operation was completed on the set associ- ated with the semaphore entry. EXAMPLES
Sample output from entering ipcs without options follows. Message Queues: T ID KEY MODE OWNER GROUP q 4 0x41002ab4 --rw------- root system Shared Memory: T ID KEY MODE OWNER GROUP m 0 0x3253bc5c --rw-rw-rw- root system m 129 0 DLrw------- root daemon Semaphores: T ID KEY MODE OWNER GROUP s 0 0x41002ab4 --ra------- root system Output is formatted differently if the environment variable CMD_ENV is set to the string svr4. For example: IPC status from /dev/kmem as of Thu Mar 26 11:31:03 1998 T ID KEY MODE OWNER GROUP Message Queues: q 4 0x41002ab4 --rw------- root system Shared Memory: m 0 0x3253bc5c --rw-rw-rw- root system m 129 0 DLrw------- root daemon Semaphores: s 0 0x41002ab4 --ra------- root system FILES
Contains user information. Contains group information. SEE ALSO
Commands: ipcrm(1) Functions: msgrcv(2), msgsnd(2), semop(2), shmat(2), shmdt(2) ipcs(1)
All times are GMT -4. The time now is 11:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy