03-22-2019
Forum Feedback: Locked and Solved Threads
Hi,
Notice in advance: When I report any feedback about the forum, I make sure that I use Google Chrome(supported browser) and check the issue there.
I shortly read the comment of RudiC that the Thread turns light blue, when it is solved. I never realized that this is the visible sign of a solved thread. It seems not very intuitive to me. I would appreciate if there's a more easy understandable mark. Maybe a changed icon for the thread (hook-icon?) in the thread list.
The same for locked threads. They are not displayed visually at all. Maybe a lock-icon in the thread list helps to recognize closed threads.
Thanks for considering.
Regards,
stomp
EDIT
I realize a lock icon came later now on a now locked thread. Maybe it was a caching issue. So please ignore feedback #2.
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
Would like to get some feedback on a scrip that I've finished writing at home for work.
Any constructive feedback from operations used to legibility, etc. would be appreciated - anything at all. It's my first real script that will be running on a clients server.
The script is... (2 Replies)
Discussion started by: Cameron
2 Replies
2. UNIX for Dummies Questions & Answers
hi,
i am VERY new to UNIX. just wanted some help on a feedback form that i have hosted on a unix server. the feedback form is in asp and doesnt work on unix. any other language to get it working ?? HELP !!! (3 Replies)
Discussion started by: shahenil
3 Replies
3. Programming
Hi
I search an exemple of scheduling Feedback algorithm, or help about how to create one.
Thanks (0 Replies)
Discussion started by: messier79
0 Replies
4. Shell Programming and Scripting
Hi
I'm looking for some feedback on kshdb, what are peoples general feeling about it etc.
Also has anyone used this as a test mechanism? I am thinking about trying to wrap a basic test script around this. (0 Replies)
Discussion started by: eeisken
0 Replies
5. Post Here to Contact Site Administrators and Moderators
perhaps offtopic.. pity this forum don't have an option 'mark this thread as solved' like some others do.. (2 Replies)
Discussion started by: orange47
2 Replies
6. What is on Your Mind?
We just added a new feature.
When tagging a thread, if you tag the thread "solved" the title of the thread will show up as blue (#0000FF) in various places (forum view, top stats, etc.)
So, if you want to show your thread as "solved" simply add a "solved" tag to the thread taglist.
... (16 Replies)
Discussion started by: Neo
16 Replies
7. Forum Support Area for Unregistered Users & Account Problems
Is it possible to retrieve all old threads of a forum?
For example, I am interested in the shell programming part for tons examples on shell scripting.
Thanks! (6 Replies)
Discussion started by: yifangt
6 Replies
8. What is on Your Mind?
Today I change the DB and the PHP code and rebuilt the database for similar threads at the end of each post, increasing from a max of 5 to a max of 10 similar threads per post:
More UNIX and Linux Forum Topics You Might Find Helpful
It was quite easy to do:
1. Increased the max size of... (17 Replies)
Discussion started by: Neo
17 Replies
LEARN ABOUT OSF1
pthread_mutex_unlock
pthread_mutex_unlock(3) Library Functions Manual pthread_mutex_unlock(3)
NAME
pthread_mutex_unlock - Unlocks the specified mutex.
LIBRARY
DECthreads POSIX 1003.1c Library (libpthread.so)
SYNOPSIS
#include <pthread.h>
int pthread_mutex_unlock(
pthread_mutex_t *mutex);
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
IEEE Std 1003.1c-1995, POSIX System Application Program Interface
PARAMETERS
Mutex to be unlocked.
DESCRIPTION
This routine unlocks the mutex specified by the mutex argument.
This routine behaves as follows, based on the type of the specified mutex: For a normal, default, or errorcheck mutex: if the mutex is
owned by the calling thread, it is unlocked with no current owner. Further, for a normal or default mutex: if the mutex is not locked or
is locked by another thread, this routine can also return [EPERM], but this is not guaranteed. For an errorcheck mutex: if the mutex is not
locked or is locked by another thread, this routine returns [EPERM]. For a recursive mutex: if the mutex is owned by the calling thread,
the lock count is decremented. The mutex remains locked and owned until the lock count reaches zero (0). When the lock count reaches zero,
the mutex becomes unlocked with no current owner.
If one or more threads are waiting to lock the specified mutex, and the mutex becomes unlocked, this routine causes one thread to unblock
and to try to acquire the mutex. The scheduling policy is used to determine which thread to unblock. For the SCHED_FIFO and SCHED_RR
policies, a blocked thread is chosen in priority order, using first-in/first-out within priorities. Note that the mutex might not be
acquired by the awakened thread if any other running thread attempts to lock the mutex first.
On Tru64 UNIX, if a signal is delivered to a thread waiting for a mutex, upon return from the signal handler, the thread resumes waiting
for the mutex as if it was not interrupted.
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 for mutex is invalid. The calling thread does not own the mutex.
ERRORS
None
RELATED INFORMATION
Functions: pthread_mutexattr_settype(3), pthread_mutex_destroy(3), pthread_mutex_init(3), pthread_mutex_lock(3), pthread_mutex_trylock(3)
Manuals: Guide to DECthreads and Programmer's Guide
delim off
pthread_mutex_unlock(3)