07-04-2010
linux, glibc 2.5
Right, before waiting on a conditional variable you must hold the mutex. But once within the 'wait' method itself the mutex will be released while waiting on the conditional variable queue (waiting for the conditional variable being signaled or broadcast.)
Once the signal arrives then 'wait' must guaranty that the mutex is acquired again before returning to the 'wait' caller. That's the basic mechanics for a conditional variable. Reacquiring the mutex, as much as I understand, is always something that one would expect implemented with the API at hand, in this case pthread.
My point is that in this pthread implementation relocking the mutex goes without a timed call, that is, the whole method could block forever if something went wrong with the thread that should have released the mutex. Therefore, it is possible that pthread_cond_timedwait would block for ever, which is exactly what one is trying to avoid by using a timed version of 'wait'.
9 More Discussions You Might Find Interesting
1. AIX
Hi all, my RS/6k 7043 150 with aix 4.3.3 takes FOREVER to log in. When I power the machine on, the boot process procedes normally and I get 2 short beeps (which I don't recall hearing before) and then I get the login window. If I log in, as root, say, the machine goes to its usual blue screen... (3 Replies)
Discussion started by: Jwoollard
3 Replies
2. Programming
When I am using msgrcv to get a message from a queue, in case of msgsnd some error, the msgrcv thread will waiting forever.
Is there some way that I can specify a time out value for this queue ? just let msgrcv wait for some time, if no message comes during this time slot, msgrcv just return... (3 Replies)
Discussion started by: Yun Gang Chen
3 Replies
3. Solaris
Hi I am very new for Solaris, I want to make some users' passwords never expired. My ssytem kernel is: 5.8
# uname -a
SunOS sspfs_svr 5.8 Generic_117000-01 sun4u sparc SUNW,Netra-240
Could you make some advice?
Thanks (5 Replies)
Discussion started by: xramm
5 Replies
4. Linux
Hi guys! I've just mounted my drive in fstab:
/dev/sdb /myfolder ext3 defaults 0 0
and rebooted linux.
I've got severel failers during booting process and also I can't login as root first time:
login: root
password:root
incorrect login
login:user
password: user
... (1 Reply)
Discussion started by: Junior Admin
1 Replies
5. IP Networking
Just looking at my ethernet interface.. I see this response... what does this mean...?
ipconfig...
lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft... (0 Replies)
Discussion started by: jimmyc
0 Replies
6. Programming
I need to use pthread_cond_timedwait, which is available in my old embedded Linux for PPC. But I don't have clock_gettime... So, I build this replacement for clock_gettime, and it seems to work:
#include <sys/time.h>
#include <time.h>
int clock_gettime_replacement(struct timespec *now) {... (1 Reply)
Discussion started by: fcolombo
1 Replies
7. Shell Programming and Scripting
I'm trying to make a little script, but I have a problem...
I'm trying to sed a list of files made with a ls > filename.txt...
Two variables (or i may call them constant because they are fixed values :D):
ststr1 and ststr2
I want to
sed s/"$ststr1"/"$ststr2"/g filename.txt >... (5 Replies)
Discussion started by: maxlamax
5 Replies
8. Red Hat
Hello All,
I was trying to install one rpm and it failed due to missing dependencies, when I try to look at the dependencies and try to install them it is asking for 100+ dependencies, did any one ever face this problem? how can we fix this?
rpm -ivh /var/tmp/erlang-R15B-02.1.el6.x86_64.rpm... (0 Replies)
Discussion started by: lovesaikrishna
0 Replies
9. UNIX for Dummies Questions & Answers
I am trying to use the forever command. I can get it to work if I do not use the w option to watch for changes and cause an automatic restart on a change to the contents of the directory being watched.
I would really like to use the watch option. Is this option fully implemented? here is an... (4 Replies)
Discussion started by: barrygordon
4 Replies
LEARN ABOUT OSF1
pthread_cond_signal
pthread_cond_signal(3) Library Functions Manual pthread_cond_signal(3)
NAME
pthread_cond_signal - Wakes at least one thread that is waiting on the specified condition variable.
LIBRARY
DECthreads POSIX 1003.1c Library (libpthread.so)
SYNOPSIS
#include <pthread.h>
int pthread_cond_signal(
pthread_cond_t *cond);
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
IEEE Std 1003.1c-1995, POSIX System Application Program Interface
PARAMETERS
Condition variable to be signaled.
DESCRIPTION
This routine unblocks at least one thread waiting on the specified condition variable cond. Calling this routine implies that data guarded
by the associated mutex has changed, thus it might be possible for one of the waiting threads to proceed. In general, only one thread will
be released.
If no threads are waiting on the specified condition variable, this routine takes no action. The signal does not propagate to the next
condition variable wait.
This routine should be called when any thread waiting on the specified condition variable might find its predicate true, but only one
thread should proceed. If more than one thread can proceed, or if any of the threads would not be able to proceed, then you must use
pthread_cond_broadcast(3).
The scheduling policy determines which thread is awakened. For policies SCHED_FIFO and SCHED_RR, a blocked thread is chosen in priority
order, using first-in/first-out (FIFO) within priorities.
If the calling thread holds the lock to the target condition variable's associated mutex while setting the variable's wait predicate, that
thread can call pthread_cond_signal(3) to signal the variable even after releasing the lock on that mutex. However, for more predictable
scheduling behavior, call pthread_cond_signal(3) before releasing the target condition variable's associated mutex.
RETURN VALUES
If an error condition occurs, this routine returns an integer value indicating the type of error. Possible return values are as follows:
Successful completion. The value specified by cond is not a valid condition variable.
ERRORS
None
RELATED INFORMATION
Functions: pthread_cond_broadcast(3), pthread_cond_destroy(3), pthread_cond_init(3), pthread_cond_timedwait(3), pthread_cond_wait(3)
Manuals: Guide to DECthreads and Programmer's Guide
delim off
pthread_cond_signal(3)