07-04-2010
Quote:
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'.
Yes, it is very possible for that to happen.
I am not sure what your understanding of how pthread_cond_timedwait works is. I would point out that once the wait time expires and is turned off, the thread is moved off the sleep queue. Likewise once a sleeping thread is signaled, even by error, it is taken off the sleep queue and the wait timer is turned off. This does not mean that it re-acquires the mutex, etc. If it takes another week before reacquiring the mutex, too bad. If it never gets the mutex back because the other thread has not released it, too bad.
If you have the Lewis & Berg book on Pthreads, this issue is discussed on pages 94 -99. Dave Butenhof also discusses this issue in his book on Pthreads. See section 3.3.2 et al.
BTW, a thought just struck me, are you trying to port a Win32 application which uses eventing to GNU/Linux?
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 OPENSOLARIS
pthread_mutexattr_settype
pthread_mutexattr_gettype(3C) Standard C Library Functions pthread_mutexattr_gettype(3C)
NAME
pthread_mutexattr_gettype, pthread_mutexattr_settype - get or set mutex type
SYNOPSIS
cc -mt [ flag... ] file... -lpthread [ library... ]
#include <pthread.h>
int pthread_mutexattr_gettype(pthread_mutexattr_t *restrict attr,
int *restrict type);
int pthread_mutexattr_settype(pthread_mutexattr_t *attr, int type);
DESCRIPTION
The pthread_mutexattr_gettype() and pthread_mutexattr_settype() functions respectively get and set the mutex type attribute. This attribute
is set in the type parameter to these functions. The default value of the type attribute is PTHREAD_MUTEX_DEFAULT.
The type of mutex is contained in the type attribute of the mutex attributes. Valid mutex types include:
PTHREAD_MUTEX_NORMAL This type of mutex does not detect deadlock. A thread attempting to relock this mutex without first unlocking
it will deadlock. Attempting to unlock a mutex locked by a different thread results in undefined behavior.
Attempting to unlock an unlocked mutex results in undefined behavior.
PTHREAD_MUTEX_ERRORCHECK This type of mutex provides error checking. A thread attempting to relock this mutex without first unlocking it
will return with an error. A thread attempting to unlock a mutex that another thread has locked will return
with an error. A thread attempting to unlock an unlocked mutex will return with an error.
PTHREAD_MUTEX_RECURSIVE A thread attempting to relock this mutex without first unlocking it will succeed in locking the mutex. The
relocking deadlock that can occur with mutexes of type PTHREAD_MUTEX_NORMAL cannot occur with this type of
mutex. Multiple locks of this mutex require the same number of unlocks to release the mutex before another
thread can acquire the mutex. A thread attempting to unlock a mutex that another thread has locked will return
with an error. A thread attempting to unlock an unlocked mutex will return with an error. This type of mutex is
only supported for mutexes whose process shared attribute is PTHREAD_PROCESS_PRIVATE.
PTHREAD_MUTEX_DEFAULT Attempting to recursively lock a mutex of this type results in undefined behavior. Attempting to unlock a mutex
of this type that was not locked by the calling thread results in undefined behavior. Attempting to unlock a
mutex of this type that is not locked results in undefined behavior. An implementation is allowed to map this
mutex to one of the other mutex types.
RETURN VALUES
Upon successful completion, the pthread_mutexattr_settype() function returns 0. Otherwise, an error number is returned to indicate the
error.
Upon successful completion, the pthread_mutexattr_gettype() function returns 0 and stores the value of the type attribute of attr in the
object referenced by the type parameter. Otherwise an error number is returned to indicate the error.
ERRORS
The pthread_mutexattr_gettype() and pthread_mutexattr_settype() functions will fail if:
EINVAL The value type is invalid.
The pthread_mutexattr_gettype() and pthread_mutexattr_settype() functions may fail if:
EINVAL The value specified by attr is invalid.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
pthread_cond_timedwait(3C), pthread_cond_wait(3C), attributes(5), standards(5)
NOTES
Application should not use a PTHREAD_MUTEX_RECURSIVE mutex with condition variables because the implicit unlock performed for
pthread_cond_wait() or pthread_cond_timedwait() will not actually release the mutex (if it had been locked multiple times). If this occurs,
no other thread can satisfy the condition of the predicate.
SunOS 5.11 23 Mar 2005 pthread_mutexattr_gettype(3C)