replacing of the mutex with POSIX semaphore Post: 302118203

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

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

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

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

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

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

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

10. Programming

Posix Semaphore Use - Releasing all resources?

I am attempting to write a program with multiple POSIX threads. I want to ensure all threads are released at the same time. I am (trying to) use a semaphore to accomplish this. Without too much irrelevant information, I declare my semaphore with 0 of 25 resources available. Is there a way...

LEARN ABOUT SUSE

xlockdisplay

XInitThreads(3) 						  XLIB FUNCTIONS						   XInitThreads(3)

NAME

       XInitThreads, XLockDisplay, XUnlockDisplay - multi-threading support

SYNTAX

       Status XInitThreads(void);

       void XLockDisplay(Display *display);

       void XUnlockDisplay(Display *display);

ARGUMENTS

       display	 Specifies the connection to the X server.

DESCRIPTION

       The XInitThreads function initializes Xlib support for concurrent threads.  This function must be the first Xlib function a multi-threaded
       program calls, and it must complete before any other Xlib call is made.	This function returns a nonzero status if initialization was suc-
       cessful; otherwise, it returns zero.  On systems that do not support threads, this function always returns zero.

       It is only necessary to call this function if multiple threads might use Xlib concurrently.  If all calls to Xlib functions are protected
       by some other access mechanism (for example, a mutual exclusion lock in a toolkit or through explicit client programming), Xlib thread ini-
       tialization is not required.  It is recommended that single-threaded programs not call this function.

       The XLockDisplay function locks out all other threads from using the specified display.	Other threads attempting to use the display will
       block until the display is unlocked by this thread.  Nested calls to XLockDisplay work correctly; the display will not actually be unlocked
       until XUnlockDisplay has been called the same number of times as XLockDisplay.  This function has no effect unless Xlib was successfully
       initialized for threads using XInitThreads.

       The XUnlockDisplay function allows other threads to use the specified display again.  Any threads that have blocked on the display are
       allowed to continue.  Nested locking works correctly; if XLockDisplay has been called multiple times by a thread, then XUnlockDisplay must
       be called an equal number of times before the display is actually unlocked.  This function has no effect unless Xlib was successfully ini-
       tialized for threads using XInitThreads.

SEE ALSO

       Xlib - C Language X Interface

X Version 11							   libX11 1.3.2 						   XInitThreads(3)

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

How to handle mutex lock?

Discussion started by: satheeshalle

4. UNIX for Dummies Questions & Answers

what is diff b/w semaphore and mutex

Discussion started by: amitpansuria