unixware.html revision e507b318e2b8f7f6a749b9fba35b1b65b560eacc
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<TITLE>Compiling Apache under UnixWare</TITLE>
</HEAD>
<BODY BGCOLOR="white" TEXT="black" LINK="blue" VLINK="navy" ALINK="red">
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Compiling Apache under UnixWare</H1>
To compile a working copy of Apache under UnixWare, there are several other
steps you may need to take. These prevent such problems as zombie processes,
bind errors, and accept errors, to name a few.
Make sure that USE_FCNTL_SERIALIZE_ACCEPT is defined (if not
defined by Apache autoconfiguration). If using the UnixWare <i>cc</i>
compiler, and you still see accept() errors, don't use compiler optimization,
or get <i>gcc</i>.
in order for Apache to work correctly on UnixWare 2.0.x. See
for UnixWare patch information.<p>
In addition, make sure that USE_FCNTL_SERIALIZE_ACCEPT is defined (if not
defined by Apache autoconfiguration). To reduce instances of connections
in FIN_WAIT_2 state, you may also want to define NO_LINGCLOSE (Apache 1.2
only).
in order for Apache to work correctly on UnixWare 2.1.x. See
for UnixWare patch information.<p>
<b>NOTE:</b> Unixware 2.1.2 and later already have patch ptf3123 included<p>
In addition, make sure that USE_FCNTL_SERIALIZE_ACCEPT is defined (if not
defined by Apache autoconfiguration). To reduce instances of connections
in FIN_WAIT_2 state, you may also want to define NO_LINGCLOSE (Apache 1.2
only).<p>
Thanks to Joe Doupnik <JRD@cc.usu.edu> and Rich Vaughn
<rvaughn@aad.com> for additional info for UnixWare builds.<p>
<!--#include virtual="footer.html" -->
</BODY>
</HTML>