Sponsored Content
Operating Systems AIX how to clean Unused semaphore?? Post 302222032 by vidyadhar85 on Wednesday 6th of August 2008 12:27:42 AM
Old 08-06-2008
you can go for ipcs(interprocess communication facility status) with following option-q to clear queue-m to clear messages-s to clear semaphore
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How do I get the unused space?

One of my Solaris 8 machines hd was about to die. So I used g4u to create an image of the 9gb drive and I put it in a 36gb drive. That solved my dieing hd problem. But.... How do I get my machine to see the unused 27gb of space? Any help would be greatly appreciated. (1 Reply)
Discussion started by: Spyzic
1 Replies

2. AIX

unused storage on AIX 4.3

Hi, How do I query for unused partition in AIX 4.3 with DAS and SAA storage? I know most unix administrator don't put all the capacity on the system at once. thanks, vene (1 Reply)
Discussion started by: venerayan
1 Replies

3. UNIX for Dummies Questions & Answers

delete the unused file

Hi All, Can you please let me know how to delete any files that have not been accessed in the past 28 days in a directory. Thanks, Arun (3 Replies)
Discussion started by: arunkumar_mca
3 Replies

4. HP-UX

HP-UX using unused HDD space

Hello, I have a system with HP-UX 11.23 installed on it. There are ~36GB of unused space on the HDD. I did a very basic installation, and it created the usual volume group /dev/vg00. When I look at the output of ioscan -funC disk, I see this (and more, but irrelevant to this post): disk ... (1 Reply)
Discussion started by: goon12
1 Replies

5. Solaris

unused disk space

i Have alloted 20G in my vmware for solaris 10, upon installation, and some distribution of disk space to /,/opt,swap i just use 19G. Can i still use the 1G? How? how to see the 1G? that i did not use? how can i use it? appreciate your responce (17 Replies)
Discussion started by: kenshinhimura
17 Replies

6. AIX

Temporarily disabling unused ethernet adapter

Hi, In our AIX 5.2 server , we have one unused ethernet adapter which doesn't have cable connection . For this interface , we are getting alerts in errpt . Could you suggesthow to stop this alert ? And sametime i would like to keep this device in ODM . Is there... (1 Reply)
Discussion started by: sekarsamy
1 Replies

7. AIX

locking down unused or unwanted ports in AIX

We have a system and we have modified the /etc/ind.conf and the /etc/services and the /etc/rc.tcpip file to turn off specific applications. I need to know what is the correct procedure for locking down unused ports that still appear to be in a listen mode even... (1 Reply)
Discussion started by: admaix
1 Replies

8. Programming

What Unix do with unused shared memory?

Hello, When creating shared memory in C, should be remove shared memory with shmctl function when don't need it. If it didn't remove, occupied shared memory stay and remain. If we create shared memory repeatedly without removing unusable shared memory, /dev/shm will full. Does Unix or... (1 Reply)
Discussion started by: pronetin
1 Replies

9. UNIX for Advanced & Expert Users

Detecting unused variables...

Hi guys... The first active code line in AudioScope.sh is set -u . This causes a complete exit if a variable is used/found but has not been allocated at the start of the program. However, apart from writing code to do the task, is there a switch to to check which variables have been... (17 Replies)
Discussion started by: wisecracker
17 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:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy