Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

466
Views
Why does sem_open work with fork() without shared memory?

This program works (I tested it), even though the semaphore is not in shared memory. Note how I create the variable once - before the fork().

On the other hand, a semaphore created with sem_init() needs to be in shared memory to work. But it's still a sem_t structure, so why doesn't it require shared memory?

Are the contents of the sem_t structure somehow different?

sem_t *s = sem_open("mysemaphore1", O_CREAT, 0600, 0);
if (fork()) {
    sleep(3);
    sem_post(s);
} else {
    sem_wait(s);
    printf("Woke\n");
}
over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

The semaphore created by sem_open() is a named semaphore. The basic purpose of named semaphore is to be used between unrelated processes. The semaphore created by sem_init() is an unnamed semaphore. It is light weight than the named semaphore and needs to be put in shared memory if used between related processes. If used between threads of the same process, it can be kept in global variable.

The pointer returned by the sem_open() is actually a pointer to a memory mapped by mmap() with MAP_SHARED flag set. Since such kind of memory persists across fork(), hence you are able to use the same variable in both parent and child to access the named semaphore.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!