>Number: 4279 >Category: os-ultrix >Synopsis: Apache complained that it doesn't know how to serialize access >when started with two LISTEN directives. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Tue Apr 20 13:30:01 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.3 >Environment: ULTRIX clinfo.rockefeller.edu 4.3 1 RISC gcc 2.8.1 >Description: N/A >How-To-Repeat: N/A >Fix: httpsd complained about its inability to serialize access to the ports. So I read PORTING, and did the following small change. In the src/include/ap_config.h I added #define USE_FCNTL_SERIALIZED_ACCEPT in #elif defined(ULTRIX) ... #endif bracket. No complains, httpsd starts and works OK. (Checked with Ben Laurie about "s" part - I use apache-ssl - and he confirmed that it is apache problem, not apache-ssl problem). >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
