Im old to Unix but new to scripting
I have a MacBook running osx that I want to use as an nfs client. The server will be a linux box with a wake on lan card. Here's the idea. Run a cron command on the mac every minute that checks if I am on my home wireless network (the linux box is wired to... (0 Replies)
m old to Unix but new to scripting
I have a MacBook running osx that I want to use as an nfs client. The server will be a linux box with a wake on lan card. Here's the idea. Run a cron command on the mac every minute that checks if I am on my home wireless network (the linux box is wired to... (6 Replies)
I have two threads: one maintains a thread-safe message queue (handle this queue at the beginning of every loop) and deals with tcp connections, the other one posts message to the former one. the problem is, while the former one was blocking at epoll_wait, it's not sure that how long until the... (0 Replies)
Hello, I'm searching for a proper way to let the kernel space ISR(implemented in a kernel module) wake up a user space thread on a hardware interrupt.
Except for sending a real-time signal, is it possible to use a semaphore?
I've searched it on google, but it seems impossible to share a... (0 Replies)
This is a very crude attempt in Bash at something that I needed but didn't seem to find in the 'sleep' command. However, I would like to be able to do it without the need for the temp file. Please go easy on me if this is already possible in some other way:
How many times have you used the... (5 Replies)
Hi all,
Is it possible to do the following in Linux (kernel 2.6.x):
- A user-space thread goes to "sleep". Using any call/mechanism
- On a hardware generated interrupt, the Interrupt handler (ISR) "wakes" the sleeping user-thread.
I have seen wait_event() and wake_up() but it appears... (1 Reply)
I'm a OS X user (MacBook Pro, OS X Lion) and I need it to wake up on Mondays, Wednesdays, Thursdays and Saturdays at 9:00 AM
on the rest of the days of the week at 7:00
I issue the following commands:
sudo pmset repeat wake MWRS 09:00:00 for the former
sudo pmset repeat wake TFU... (1 Reply)
Discussion started by: scrutinizerix
1 Replies
LEARN ABOUT HPUX
pthread_mutex_unlock
pthread_mutex_unlock(3T)pthread_mutex_unlock(3T)NAME
pthread_mutex_unlock() - unlock a mutex.
SYNOPSIS PARAMETERS
mutex Pointer to the mutex to be unlocked.
DESCRIPTION
The function is called by the owner of the mutex referenced by mutex to unlock the mutex. The manner in that the mutex is released is
dependent upon the mutex's type attribute. For normal and default mutexes, undefined behavior will result if is called on an unlocked
mutex or by a thread that is not the current owner. For recursive and error-checking mutexes, an error is returned if is called on an
unlocked mutex or by a thread which is not the current owner.
For recursive mutexes, the owner must call as many times as the mutex was locked before another thread can lock the mutex.
If there are threads blocked on the mutex referenced by mutex when releases the mutex, the scheduling policy is used to determine which
thread will acquire the mutex next.
RETURN VALUE
Upon successful completion, returns zero. Otherwise, an error number is returned to indicate the error (the variable is not set).
ERRORS
For each of the following conditions, if the condition is detected, the function returns the corresponding error number:
[EINVAL] mutex is not an initialized mutex.
[EPERM] The calling thread does not own mutex. On HP-UX, this error is not detected for or mutexes.
[EFAULT] mutex parameter points to an illegal address.
AUTHOR
was derived from the IEEE POSIX P1003.1c standard and HP extensions.
SEE ALSO pthread_mutex_init(3T), pthread_mutex_destroy(3T), pthread_mutex_lock(3T), pthread_mutex_trylock(3T).
STANDARDS CONFORMANCE
Pthread Library pthread_mutex_unlock(3T)