os-qnx/2296: SERIALIZED_ACCEPT on QNX

[Rob Saccoccio <ro...@InfiniteTechnology.com>]

>Number:         2296
>Category:       os-qnx
>Synopsis:       SERIALIZED_ACCEPT on QNX
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Wed May 27 08:50:01 PDT 1998
>Last-Modified:
>Originator:     robs@InfiniteTechnology.com
>Organization:
apache
>Release:        1.3b7
>Environment:
>Description:
There is no form of SERIALIZED_ACCEPT defined for QNX.

USE_FLOCK_SERIALIZED_ACCEPT and USE_FCNTL_SERIALIZED_ACCEPT both seem 
to work fine.  Admittedly, I can't create much of a load.  I suspect
some form of SERIALIZED_ACCEPT would be better than none.  Based on the 
reading it seems USE_FLOCK_SERIALIZED_ACCEPT is the better choice.

If there is some way of conclusively determining appropriate functioning
or for determining which is better/faster, please let me know.
>How-To-Repeat:

>Fix:
Here's a diff -c for conf.h...

*** conf-orig.h	Mon May 11 15:59:01 1998
--- conf.h	Wed May 27 11:43:08 1998
***************
*** 626,631 ****
--- 626,632 ----
  #include <unix.h>
  #define HAVE_MMAP 1
  #define USE_POSIX_SCOREBOARD
+ #define USE_FLOCK_SERIALIZED_ACCEPT
  #define HAVE_SYSLOG 1
  
  #elif defined(LYNXOS)
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]


>uname -a
QNX 23 G 424 PCI 32

Watcom 10.6