Is accept() thread-safe?

by

Yes. This is a common way to design multithreaded servers and accepted design practice.

You can also fork several times and have the child processes call accept, this will allow you to do multithreading without needing a threads library. Older servers do this.

More Related Contents:

  1. Wake up thread blocked on accept() call
  2. Program received signal SIGPIPE, Broken pipe
  3. What’s the correct answer about getservbyname?
  4. POSIX threads and signals
  5. How do I change a TCP socket to be non-blocking?
  6. Sending file descriptor by Linux socket
  7. POSIX API call to list all the pthreads running in a process
  8. How to return a value from pthread threads in C?
  9. Error: Address already in use while binding socket with address but the port number is shown free by `netstat`
  10. Turn a simple socket into an SSL socket
  11. Is it OK to call pthread_exit from main?
  12. Is there a way to flush a POSIX socket?
  13. Using sys/socket.h functions on windows
  14. How to signal select() to return immediately?
  15. Bind failed: Address already in use
  16. Interprocess mutex with pthreads
  17. socket connect() vs bind()
  18. Socketpair() in C/Unix
  19. Writing to a closed, local TCP socket not failing
  20. Problems with SO_BINDTODEVICE Linux socket option
  21. Using C/Pthreads: do shared variables need to be volatile?
  22. Does pthread_mutex_lock contains memory fence instruction? [duplicate]
  23. Is it possible to access/update the child thread’s resource from parent thread?
  24. Linux/POSIX equivalent for Win32’s CreateEvent, SetEvent, WaitForSingleObject
  25. Is it possible (and safe) to make an accepting socket non-blocking?
  26. How to reset a socket back to blocking mode (after I set it to nonblocking mode)?
  27. How to set up pthreads on windows?
  28. What can cause a “Resource temporarily unavailable” on sock send() command
  29. Pthreads vs. OpenMP
  30. Bind error while recreating socket

Leave a Comment