Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Silly question about a process Post 302142517 by porter on Friday 26th of October 2007 06:51:51 PM
Old 10-26-2007
There are two type of threads.

1. Kernel threads, implemented by the kernel, synchronisation is performed by the kernel.

2. User threads, the kernel knows nothing about the threads hence no need for kernel semaphores, only user semaphores are needed.

As a programmer, if you use the an API such as pthreads you do not care whether the threads are implemented by the kernel or by a user library.
 

10 More Discussions You Might Find Interesting

1. Solaris

Silly question

Are GNOME or javadsktop supported of the box on Solaris 10 on Ultra (SUNBlade 1500) ? I'could switch desktops to KDE at CDE logon. But when I tried to use the JavaDesktop it simply returns me back to the log on screen of CDE. How do I conigure to the latest GNOME and.or JavaDesktop if... (3 Replies)
Discussion started by: miket
3 Replies

2. Solaris

Silly Cdrom burn question

Probably a silly question but one I dont know the answer to all the same.. I downloaded the following from sun - solaris 9 part 1 of the software sol-9-u7-sparc-v1.zip When I unzip it I get an iso file. How do I burn it to a cdrom and be able to insert it to solaris machine so that it will... (3 Replies)
Discussion started by: frustrated1
3 Replies

3. Shell Programming and Scripting

Silly newbie question on special characters!

Hello again Gurus, Can someone please direct me to an online source that specifically explains what characters like mean within if statements? or scripts in general, I have found information about the different letter options you can specify for an if statment, but I get really confused with the... (3 Replies)
Discussion started by: charliemp3
3 Replies

4. UNIX for Dummies Questions & Answers

silly question

How do I go about finding the number of unique words in a file. (3 Replies)
Discussion started by: EECSDAVE
3 Replies

5. UNIX for Dummies Questions & Answers

Silly question on printing for loop in AWK

Hi, One silly question. I would like to add statement like below and append to a file. I used the below code; however, it does not work. Can anyone please tell me what mistakes I have made? awk ' { for (i=1;i<=563;i++) print i }'>>output.txt Thanks. -Jason (1 Reply)
Discussion started by: ahjiefreak
1 Replies

6. Solaris

Silly question regarding SSH.

Hi Guys, I have installed SSH package on server as well as clients. I think I need to these steps next. Login as root on the server. 1) ssh-keygen -b 1024 -t rsa -f /etc/ssh_hosts_key.pub -N " " Login to root as the user. 2)ssh_keygen -b 1024 -t rsa Enter the phrase Basically this... (3 Replies)
Discussion started by: nitinkgoud
3 Replies

7. UNIX for Dummies Questions & Answers

silly question ..

hi all last week i had appeared for an interview where they asked me as u work on windows & unix tell me what are the advantages of UNIX over windows & vice versa ..i gave 2-3 reasons but when i told that unix is more secure than windows he asked me how ? i was speechless. then i googled about... (6 Replies)
Discussion started by: zedex
6 Replies

8. Solaris

I have a silly question

Can anyone tell me where is the best place to put my own system related scripts on a solaris server. I usually place my scripts in /usr/sbin/<my_name>, but that is only because my senior sysadmin used to do that. What does the "unix etiquette" say? (8 Replies)
Discussion started by: soliberus
8 Replies

9. Shell Programming and Scripting

A silly question

FILENAME is a variable. Is there really any difference between "$FILENAME.sh" and "$FILENAME".sh ? (5 Replies)
Discussion started by: proactiveaditya
5 Replies

10. Post Here to Contact Site Administrators and Moderators

Might be silly question

Hi Team, In case if i want to delete one of my posting thread.. can i delete that? Just asking to know.. (5 Replies)
Discussion started by: darling
5 Replies
SEM_OVERVIEW(7) 					     Linux Programmer's Manual						   SEM_OVERVIEW(7)

NAME
sem_overview - overview of POSIX semaphores DESCRIPTION
POSIX semaphores allow processes and threads to synchronize their actions. A semaphore is an integer whose value is never allowed to fall below zero. Two operations can be performed on semaphores: increment the semaphore value by one (sem_post(3)); and decrement the semaphore value by one (sem_wait(3)). If the value of a semaphore is currently zero, then a sem_wait(3) operation will block until the value becomes greater than zero. POSIX semaphores come in two forms: named semaphores and unnamed semaphores. Named semaphores A named semaphore is identified by a name of the form /somename; that is, a null-terminated string of up to NAME_MAX-4 (i.e., 251) characters consisting of an initial slash, followed by one or more characters, none of which are slashes. Two processes can operate on the same named semaphore by passing the same name to sem_open(3). The sem_open(3) function creates a new named semaphore or opens an existing named semaphore. After the semaphore has been opened, it can be operated on using sem_post(3) and sem_wait(3). When a process has finished using the semaphore, it can use sem_close(3) to close the semaphore. When all processes have finished using the semaphore, it can be removed from the system using sem_unlink(3). Unnamed semaphores (memory-based semaphores) An unnamed semaphore does not have a name. Instead the semaphore is placed in a region of memory that is shared between multiple threads (a thread-shared semaphore) or processes (a process-shared semaphore). A thread-shared semaphore is placed in an area of memory shared between the threads of a process, for example, a global variable. A process-shared semaphore must be placed in a shared memory region (e.g., a System V shared memory segment created using shmget(2), or a POSIX shared memory object built created using shm_open(3)). Before being used, an unnamed semaphore must be initialized using sem_init(3). It can then be operated on using sem_post(3) and sem_wait(3). When the semaphore is no longer required, and before the memory in which it is located is deallocated, the semaphore should be destroyed using sem_destroy(3). The remainder of this section describes some specific details of the Linux implementation of POSIX semaphores. Versions Prior to kernel 2.6, Linux supported only unnamed, thread-shared semaphores. On a system with Linux 2.6 and a glibc that provides the NPTL threading implementation, a complete implementation of POSIX semaphores is provided. Persistence POSIX named semaphores have kernel persistence: if not removed by sem_unlink(3), a semaphore will exist until the system is shut down. Linking Programs using the POSIX semaphores API must be compiled with cc -pthread to link against the real-time library, librt. Accessing named semaphores via the filesystem On Linux, named semaphores are created in a virtual filesystem, normally mounted under /dev/shm, with names of the form sem.somename. (This is the reason that semaphore names are limited to NAME_MAX-4 rather than NAME_MAX characters.) Since Linux 2.6.19, ACLs can be placed on files under this directory, to control object permissions on a per-user and per-group basis. NOTES
System V semaphores (semget(2), semop(2), etc.) are an older semaphore API. POSIX semaphores provide a simpler, and better designed inter- face than System V semaphores; on the other hand POSIX semaphores are less widely available (especially on older systems) than System V semaphores. EXAMPLE
An example of the use of various POSIX semaphore functions is shown in sem_wait(3). SEE ALSO
sem_close(3), sem_destroy(3), sem_getvalue(3), sem_init(3), sem_open(3), sem_post(3), sem_unlink(3), sem_wait(3), pthreads(7), shm_over- view(7) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-05-03 SEM_OVERVIEW(7)
All times are GMT -4. The time now is 10:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy