11-07-2010
semaphore
each process should print its process id ,parent id and child id...i just wanted to check if my semaphores are ok....thats all
10 More Discussions You Might Find Interesting
1. Programming
Dear Reader,
I'm in a multiprocess environment working with shared mem and semaphores as mutex.. The problem is -- If one of the process hooked up with the semaphore and accessing the shared mem, terminates abruptly ( or got killed ), other process which are in want of the semaphore are... (1 Reply)
Discussion started by: joseph_shibu
1 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
I am using HP 10.20 on A 9000/785. My question is:
If I am the only person logged in as root at the moment, how many "semaphore proccesses" should I have?? Is it only one, or it is relevant to other system proccesses?
Here is what I get listing the current semaphores
# ipcs -sp... (1 Reply)
Discussion started by: guest100
1 Replies
3. Programming
Hi there,
Could someone please confirm which POSIX semaphore routines should be used for a multiprocess (and not multithreaded) environment?
sys/sem.h definitely works. but the routines, semget, semctl, semop are pretty unwieldy. So, I am looking for an easier way out.
From the man pages... (2 Replies)
Discussion started by: qntmteleporter
2 Replies
4. Shell Programming and Scripting
Hi Friends,
If i execute this command it comes back with 300 lines:
ipcs|grep cerebrus >>> i would like to clear the semaphores but ipcrm can remove one id at a time. is there a quicker way of removing semaphores maybe using awk?
Regards, (1 Reply)
Discussion started by: kekanap
1 Replies
5. Programming
been searching around on how to use an up and down function with semaphores but i can't find an example. i looked into using: "semop" but i have no idea how to use it. I have been able to declared the semaphores using semget and initializing them using semctl. (7 Replies)
Discussion started by: ddx08
7 Replies
6. UNIX for Advanced & Expert Users
Hello, first of all I apologize if this thread is not in the correct section of this forum, but this one just seemed the most appropriate.
The question I have does not concern Unix specifically, it applies to virtually any OS, however it is in Unix where I learned about this problem.
So, the... (8 Replies)
Discussion started by: Watto86
8 Replies
7. Programming
Hello,
Iam trying to implement the sleeping barber problem using semaphores and running on UNIX machine. Iam linking it to the thread libraries :
bash-2.03$ g++ sleepingBarber.cpp -lpthread -o sleeping
but when i execute it i get the following error:
bash-2.03$ sleeping
Starting Program... (4 Replies)
Discussion started by: mohit.choudhary
4 Replies
8. Programming
Hello,
I was doing an exercise of semaphores and shared memory, namely the barbers:
-B number of barbers
-S number of chairs
-C number of customers.
I have done already and I compiled the code, but when run I get an error segment. Can not be and it took several days.
If anyone sees the error... (2 Replies)
Discussion started by: ciudadwifi
2 Replies
9. Programming
Hello Everybody,
I am building a server. this server contains some data. Clients may modify this data or read this data.
If a client is reading the data and at the same time another client is modifying the data then at this case the reading client may read some false data (some old mixed with... (1 Reply)
Discussion started by: Omar_Mokhtar
1 Replies
10. Solaris
Hi,
Can somebody please explain me what semaphores are? there purpose? and there effects?
Thanks in advance:) (0 Replies)
Discussion started by: Laxxi
0 Replies
IPCS(1) BSD General Commands Manual IPCS(1)
NAME
ipcs -- report System V interprocess communication facilities status
SYNOPSIS
ipcs [-abcMmopQqSsTt]
DESCRIPTION
The ipcs utility provides information on System V interprocess communication (IPC) facilities on the system.
The options are as follows:
-a Show the maximum amount of information possible when displaying active semaphores, message queues, and shared memory segments. (This
is shorthand for specifying the -b, -c, -o, -p, and -t options.)
-b Show the maximum allowed sizes for active semaphores, message queues, and shared memory segments. The ``maximum allowed size'' is
the maximum number of bytes in a message on a message queue, the size of a shared memory segment, or the number of semaphores in a
set of semaphores.
-c Show the creator's name and group for active semaphores, message queues, and shared memory segments.
-M Display system information about shared memory.
-m Display information about active shared memory segments.
-o Show outstanding usage for active message queues, and shared memory segments. The ``outstanding usage'' is the number of messages in
a message queue, or the number of processes attached to a shared memory segment.
-p Show the process ID information for active semaphores, message queues, and shared memory segments. The ``process ID information'' is
the last process to send a message to or receive a message from a message queue, the process that created a semaphore, or the last
process to attach or detach a shared memory segment.
-Q Display system information about messages queues.
-q Display information about active message queues.
-S Display system information about semaphores.
-s Display information about active semaphores.
-T Display system information about shared memory, message queues and semaphores.
-t Show access times for active semaphores, message queues, and shared memory segments. The access times is the time of the last con-
trol operation on an IPC object, the last send or receive of a message, the last attach or detach of a shared memory segment, or the
last operation on a semaphore.
If none of the -M, -m, -Q, -q, -S, or -s options are specified, information about all active IPC facilities is listed.
RESTRICTIONS
System data structures may change while ipcs is running; the output of ipcs is not guaranteed to be consistent.
BUGS
This manual page is woefully incomplete, because it does not at all attempt to explain the information printed by ipcs.
SEE ALSO
ipcrm(1)
AUTHORS
Thorsten Lockert <tholo@sigmasoft.com>
BSD
June 18, 1994 BSD