ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
pthread mutexes, condition variables, and read/write locks are implemented as user space libraries, there are no system calls directly associated with functions that operate on them - there are a number of different ways to implement them. ie FIFOS, mmap'd files and so on. on the other hand, you have SYSV semaphores, which are implemented in the kernel as system calls. see man ipc, which will lead u to semop and friends. for pthread functions, try:
man pthread_mutex_lock, man pthread_cond_wait, man pthread_rwlock_rdlock
If I have a function setup for common reference of searching/push/poping a pointer chain structure system, with, lets say syntax for read locking when merely searching the chain, and write locking for when chain elements are created/deleted, is there anyway to allow the same thread to call the function from within the function using BOTH a write and read lock?
Basically, during the creation phase, userInfo will call itself inorder to make user 'userID' is unique for this user. Is there anyway to allow recursive read/write calls to the same function with both a read/write lock under the same thread to make something like this possible? Mutex locks recursive calling within the same thread works, but, it would be nice to have read/write locking instead - quicker access to shared resources.