difference between Mutex and semaphores Post: 302106372

10 More Discussions You Might Find Interesting

1. Programming

Threads and Mutex

Hi all, I am working in a UNIX/C environment. I would like to understand more about MUTEX and Threads. Can someone explain me these concepts and how they are related. Vijay

2. UNIX for Dummies Questions & Answers

mutex

Can anyone explain me what mutexes are in multithreading environment?

3. Shell Programming and Scripting

mutex in shell programing

A shell in crontab per 5 min write a file B shell in crontab per 6 min read a file how to lock the share file a ;avioid confilict in write and read? Thx : -)

4. Programming

Hi, I have two tasks 'Read' and 'Write' which reads and writes on a file "abc.txt" respectively. Now I need to restrict the Write operation on the file while Read is going on, But can allow two Reads at a time. ie. two Reads can happen simultaneously, but Write can't happen at Read is going on. ...

5. UNIX for Dummies Questions & Answers

what is diff b/w semaphore and mutex

can u tell me what is the exact difference b/w mutex and semaphore and what is the diff b/w counting semaphore and binary semaphore amit

6. Shell Programming and Scripting

Mutex in Perl

Hello Everyone, I just joined this forum and this is my first post. I would like to know how can I impliment basic read/write locks in perl. I have a database (file) which can be accessed simultaneously but has to be locked while writing. If there is no such support in perl, my next...

7. Programming

Mutex will not work

I am trying to use mutex in my multi-tread project, but they don't seem to work. I have created a simple demonstration of the problem. This is NOT how I would use a mutex, only a demonstration of the problem: #include <stdio.h> #include <pthread.h> int main() { int val; ...

8. Programming

Mutex lock question

Hi all, I have a scenario where I need to use the mutex locks. The mutex locks are working fine, but sometimes I am getting into the dead lock situation. Below is the summary of my code : MUTEX LOCK performTask(); MUTEX UNLOCK. In some cases I get into the situation where...

9. Programming

pthread and mutex question

Hello, I have got some issue with the struct variable with passed arguments the variable in the sturct is only recognize the last value their assigned to I'm pretty confused why the mutex didn't work out here is my program: #include<stdio.h> #include<pthread.h> pthread_mutex_t lock...

10. Programming

Can Mutex be replaced with anything?

Hi All, To avoid race condition, instead of using mutex, semaphore, spinlock etc.... Is there any other mechanism by which we can avoid race condition in an multi-threading environment. -Thanks

LEARN ABOUT MOJAVE

ipcs

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

10 More Discussions You Might Find Interesting

1. Programming

Threads and Mutex

Discussion started by: vthasan

2. UNIX for Dummies Questions & Answers

mutex

Discussion started by: sagar

3. Shell Programming and Scripting

mutex in shell programing

Discussion started by: zz_xm

4. Programming

How to handle mutex lock?

Discussion started by: satheeshalle