How do I recover a semaphore when the process that decremented it to zero crashes?

by

Turns out there isn’t a way to reliably recover the semaphore. Sure, anyone can post_sem() to the named semaphore to get the count to increase past zero again, but how to tell when such a recovery is needed? The API provided is too limited and doesn’t indicate in any way when this has happened.

Beware of the ipc tools also available — the common tools ipcmk, ipcrm, and ipcs are only for the outdated SysV semaphores. They specifically do not work with the new POSIX semaphores.

But it looks like there are other things that can be used to lock things, which the operating system does automatically release when an application dies in a way that cannot be caught in a signal handler. Two examples: a listening socket bound to a particular port, or a lock on a specific file.

I decided the lock on a file is the solution I needed. So instead of a sem_wait() and sem_post() call, I’m using:

lockf( fd, F_LOCK, 0 )

and

lockf( fd, F_ULOCK, 0 )

When the application exits in any way, the file is automatically closed which also releases the file lock. Other client apps waiting for the “semaphore” are then free to proceed as expected.

Thanks for the help, guys.

UPDATE:

12 years later, thought I should point out that posix mutexes do have a “robust” attribute. That way, if the owner of the mutex gets killed or exits, the next user to lock the mutex will get the non-error return value of EOWNERDEAD, allowing the mutex to be recovered. This will make it similar to the file and socket locking solution. Look up pthread_mutexattr_setrobust() and pthread_mutex_consistent() for details. Thanks, Reinier Torenbeek, for this hint.

More Related Contents:

  1. how to install gcc 4.9.2 on RHEL 7.4
  2. make -j 8 g++: internal compiler error: Killed (program cc1plus)
  3. Multiple glibc libraries on a single host
  4. How do the likely/unlikely macros in the Linux kernel work and what is their benefit?
  5. How to add a default include path for GCC in Linux?
  6. How can I link to a specific glibc version?
  7. How to invoke a system call via syscall or sysenter in inline assembly?
  8. Static link of shared library function in gcc
  9. How to print the ld(linker) search path
  10. Calling printf in x86_64 using GNU assembler
  11. How to compile a 32-bit binary on a 64-bit linux machine with gcc/cmake
  12. Compiling multithread code with g++
  13. “/usr/bin/ld: cannot find -lz”
  14. How to specify the library version to use at link time?
  15. Can _start be the thumb function?
  16. Where to get iostream.h
  17. How to change the default GCC compiler in Ubuntu?
  18. How can I select a static library to be linked while ARM cross compiling?
  19. What is the ‘soname’ option for building shared libraries for?
  20. Force gcc to compile 32 bit programs on 64 bit platform
  21. How do you link to a specific version of a shared library in GCC
  22. How to include all objects of an archive in a shared object?
  23. get string length in inline GNU Assembler
  24. Make install, but not to default directories?
  25. Install gcc on linux with no root privilege
  26. Where are include files stored – Ubuntu Linux, GCC
  27. Do I need -D_REENTRANT with -pthreads?
  28. Does gcc have any options to add version info in ELF binary file?
  29. How to convert Linux 32-bit gcc inline assembly to 64-bit code? [closed]
  30. How to set RPATH and RUNPATH with GCC/LD?

Leave a Comment