diff options
| author |   hongbotian <hongbo.tianhongbo@huawei.com> | 2015-11-30 01:45:08 -0500 |
|---|---|---|
| committer | hongbotian <hongbo.tianhongbo@huawei.com> | 2015-11-30 01:45:08 -0500 |
| commit | e8ec7aa8e38a93f5b034ac74cebce5de23710317 (patch) | |
| tree | aa031937bf856c1f8d6ad7877b8d2cb0224da5ef /rubbos/app/httpd-2.0.64/docs/manual/platform | |
| parent | cc40af334e619bb549038238507407866f774f8f (diff) | |
upload http
JIRA: BOTTLENECK-10
Change-Id: I7598427ff904df438ce77c2819ee48ac75ffa8da
Signed-off-by: hongbotian <hongbo.tianhongbo@huawei.com>
Diffstat (limited to 'rubbos/app/httpd-2.0.64/docs/manual/platform')
18 files changed, 5052 insertions, 0 deletions
diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/ebcdic.html b/rubbos/app/httpd-2.0.64/docs/manual/platform/ebcdic.html new file mode 100644 index 00000000..a48afa88 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/ebcdic.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: ebcdic.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: ebcdic.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/ebcdic.html.en b/rubbos/app/httpd-2.0.64/docs/manual/platform/ebcdic.html.en new file mode 100644 index 00000000..9fd5da46 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/ebcdic.html.en @@ -0,0 +1,584 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>The Apache EBCDIC Port - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>The Apache EBCDIC Port</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/platform/ebcdic.html" title="English"> en </a> | +<a href="../ko/platform/ebcdic.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div> + + + <div class="warning"><strong>Warning:</strong> This document + has not been updated to take into account changes made in + the 2.0 version of the Apache HTTP Server. Some of the + information may still be relevant, but please use it with care. + </div> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#overview">Overview of the Apache EBCDIC Port</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#design">Design Goals</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#technical">Technical Solution</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#porting">Porting Notes</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#document">Document Storage Notes</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#modules">Apache Modules' Status</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#third-party">Third Party Modules' Status</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="overview" id="overview">Overview of the Apache EBCDIC Port</a></h2> + + + + <p>Version 1.3 of the Apache HTTP Server is the first version + which includes a port to a (non-ASCII) mainframe machine which + uses the EBCDIC character set as its native codeset.</p> + + <p>(It is the SIEMENS family of mainframes running the <a href="http://www.siemens.de/servers/bs2osd/osdbc_us.htm">BS2000/OSD + operating system</a>. This mainframe OS nowadays features a + SVR4-derived POSIX subsystem).</p> + + <p>The port was started initially to</p> + + <ul> + <li>prove the feasibility of porting <a href="http://dev.apache.org/">the Apache HTTP server</a> to + this platform</li> + + <li>find a "worthy and capable" successor for the venerable + <a href="http://www.w3.org/Daemon/">CERN-3.0</a> daemon + (which was ported a couple of years ago), and to</li> + + <li>prove that Apache's preforking process model can on this + platform easily outperform the accept-fork-serve model used + by CERN by a factor of 5 or more.</li> + </ul> + + <p>This document serves as a rationale to describe some of the + design decisions of the port to this machine.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="design" id="design">Design Goals</a></h2> + + + + <p>One objective of the EBCDIC port was to maintain enough + backwards compatibility with the (EBCDIC) CERN server to make + the transition to the new server attractive and easy. This + required the addition of a configurable method to define + whether a HTML document was stored in ASCII (the only format + accepted by the old server) or in EBCDIC (the native document + format in the POSIX subsystem, and therefore the only realistic + format in which the other POSIX tools like <code>grep</code> or + <code>sed</code> could operate on the documents). The current + solution to this is a "pseudo-MIME-format" which is intercepted + and interpreted by the Apache server (see below). Future versions + might solve the problem by defining an "ebcdic-handler" for all + documents which must be converted.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="technical" id="technical">Technical Solution</a></h2> + + + + <p>Since all Apache input and output is based upon the BUFF + data type and its methods, the easiest solution was to add the + conversion to the BUFF handling routines. The conversion must + be settable at any time, so a BUFF flag was added which defines + whether a BUFF object has currently enabled conversion or not. + This flag is modified at several points in the HTTP + protocol:</p> + + <ul> + <li><strong>set</strong> before a request is received + (because the request and the request header lines are always + in ASCII format)</li> + + <li><strong>set/unset</strong> when the request body is + received - depending on the content type of the request body + (because the request body may contain ASCII text or a binary + file)</li> + + <li><strong>set</strong> before a reply header is sent + (because the response header lines are always in ASCII + format)</li> + + <li><strong>set/unset</strong> when the response body is sent + - depending on the content type of the response body (because + the response body may contain text or a binary file)</li> + </ul> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="porting" id="porting">Porting Notes</a></h2> + + + + <ol> + <li> + <p>The relevant changes in the source are <code>#ifdef</code>'ed + into two categories:</p> + + <dl> + <dt><code><strong>#ifdef + CHARSET_EBCDIC</strong></code></dt> + + <dd> + <p>Code which is needed for any EBCDIC based machine. + This includes character translations, differences in + contiguity of the two character sets, flags which + indicate which part of the HTTP protocol has to be + converted and which part doesn't <em>etc.</em></p> + </dd> + + <dt><code><strong>#ifdef _OSD_POSIX</strong></code></dt> + + <dd> + <p>Code which is needed for the SIEMENS BS2000/OSD + mainframe platform only. This deals with include file + differences and socket implementation topics which are + only required on the BS2000/OSD platform.</p> + </dd> + </dl> + </li> + + <li> + <p>The possibility to translate between ASCII and EBCDIC at + the socket level (on BS2000 POSIX, there is a socket option + which supports this) was intentionally <em>not</em> chosen, + because the byte stream at the HTTP protocol level consists + of a mixture of protocol related strings and non-protocol + related raw file data. HTTP protocol strings are always + encoded in ASCII (the <code>GET</code> request, any Header: lines, + the chunking information <em>etc.</em>) whereas the file transfer + parts (<em>i.e.</em>, GIF images, CGI output <em>etc.</em>) + should usually be just "passed through" by the server. This + separation between "protocol string" and "raw data" is + reflected in the server code by functions like <code>bgets()</code> + or <code>rvputs()</code> for strings, and functions like + <code>bwrite()</code> for binary data. A global translation + of everything would therefore be inadequate.</p> + + <p>(In the case of text files of course, provisions must be + made so that EBCDIC documents are always served in + ASCII)</p> + </li> + + <li> + <p>This port therefore features a built-in protocol level + conversion for the server-internal strings (which the + compiler translated to EBCDIC strings) and thus for all + server-generated documents. The hard coded ASCII escapes + <code>\012</code> and <code>\015</code> which are ubiquitous + in the server code are an exception: they are already the binary + encoding of the ASCII <code>\n</code> and <code>\r</code> and + must not be converted to ASCII a second time. + This exception is only relevant for server-generated strings; + and <em>external</em> EBCDIC documents are not expected to + contain ASCII newline characters.</p> + </li> + + <li> + <p>By examining the call hierarchy for the BUFF management + routines, I added an "ebcdic/ascii conversion layer" which + would be crossed on every puts/write/get/gets, and a + conversion flag which allowed enabling/disabling the + conversions on-the-fly. Usually, a document crosses this + layer twice from its origin source (a file or CGI output) to + its destination (the requesting client): <code>file -> + Apache</code>, and <code>Apache -> client</code>.</p> + + <p>The server can now read the header lines of a CGI-script + output in EBCDIC format, and then find out that the remainder + of the script's output is in ASCII (like in the case of the + output of a WWW Counter program: the document body contains a + GIF image). All header processing is done in the native + EBCDIC format; the server then determines, based on the type + of document being served, whether the document body (except + for the chunking information, of course) is in ASCII already + or must be converted from EBCDIC.</p> + </li> + + <li> + <p>For Text documents (MIME types text/plain, text/html + <em>etc.</em>), an implicit translation to ASCII can be + used, or (if the users prefer to store some documents in + raw ASCII form for faster serving, or because the files + reside on a NFS-mounted directory tree) can be served + without conversion.</p> + + <p><strong>Example:</strong></p> + + <p>to serve files with the suffix <code>.ahtml</code> as a + raw ASCII <code>text/html</code> document without implicit + conversion (and suffix <code>.ascii</code> as ASCII + <code>text/plain</code>), use the directives:</p> + + <div class="example"><p><code> + AddType text/x-ascii-html .ahtml <br /> + AddType text/x-ascii-plain .ascii + </code></p></div> + + <p>Similarly, any <code>text/foo</code> MIME type can be + served as "raw ASCII" by configuring a MIME type + "<code>text/x-ascii-foo</code>" for it using + <code>AddType</code>.</p> + </li> + + <li> + <p>Non-text documents are always served "binary" without + conversion. This seems to be the most sensible choice for, + .<em>e.g.</em>, GIF/ZIP/AU file types. This of course + requires the user to copy them to the mainframe host using + the "<code>rcp -b</code>" binary switch.</p> + </li> + + <li> + <p>Server parsed files are always assumed to be in native + (<em>i.e.</em>, EBCDIC) format as used on the machine, and + are converted after processing.</p> + </li> + + <li> + <p>For CGI output, the CGI script determines whether a + conversion is needed or not: by setting the appropriate + Content-Type, text files can be converted, or GIF output can + be passed through unmodified. An example for the latter case + is the wwwcount program which we ported as well.</p> + </li> + + </ol> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="document" id="document">Document Storage Notes</a></h2> + + + + <h3><a name="binary" id="binary">Binary Files</a></h3> + + + + <p>All files with a <code>Content-Type:</code> which does not + start with <code>text/</code> are regarded as <em>binary + files</em> by the server and are not subject to any conversion. + Examples for binary files are GIF images, gzip-compressed files + and the like.</p> + + <p>When exchanging binary files between the mainframe host and + a Unix machine or Windows PC, be sure to use the ftp "binary" + (<code>TYPE I</code>) command, or use the + <code>rcp -b</code> command from the mainframe host (the + <code>-b</code> switch is not supported in unix + <code>rcp</code>'s).</p> + + + + <h3><a name="text" id="text">Text Documents</a></h3> + + + + <p>The default assumption of the server is that Text Files + (<em>i.e.</em>, all files whose <code>Content-Type:</code> + starts with <code>text/</code>) are stored in the native + character set of the host, EBCDIC.</p> + + + + <h3><a name="ssi" id="ssi">Server Side Included Documents</a></h3> + + + + <p>SSI documents must currently be stored in EBCDIC only. + No provision is made to convert it from ASCII before + processing.</p> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="modules" id="modules">Apache Modules' Status</a></h2> + + + + <table class="bordered"> + <tr> + <th>Module</th> + <th>Status</th> + <th>Notes</th> + </tr> + + <tr> + <td><code class="module"><a href="../mod/core.html">core</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_access.html">mod_access</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_actions.html">mod_actions</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_asis.html">mod_asis</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_auth.html">mod_auth</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_auth_anon.html">mod_auth_anon</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_auth_dbm.html">mod_auth_dbm</a></code></td> + <td class="centered">?</td> + <td>with own <code>libdb.a</code></td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_autoindex.html">mod_autoindex</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_cern_meta.html">mod_cern_meta</a></code></td> + <td class="centered">?</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code>mod_digest</code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_so.html">mod_so</a></code></td> + <td class="centered">-</td> + <td>no shared libs</td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_env.html">mod_env</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_example.html">mod_example</a></code></td> + <td class="centered">-</td> + <td>(test bed only)</td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_expires.html">mod_expires</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_headers.html">mod_headers</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_imap.html">mod_imap</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_info.html">mod_info</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code>mod_log_agent</code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code>mod_log_referer</code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_mime_magic.html">mod_mime_magic</a></code></td> + <td class="centered">?</td> + <td>not ported yet</td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_negotiation.html">mod_negotiation</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code></td> + <td class="centered">+</td> + <td>untested</td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_setenvif.html">mod_setenvif</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_speling.html">mod_speling</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_status.html">mod_status</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_unique_id.html">mod_unique_id</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_userdir.html">mod_userdir</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_usertrack.html">mod_usertrack</a></code></td> + <td class="centered">?</td> + <td>untested</td> + </tr> + </table> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="third-party" id="third-party">Third Party Modules' Status</a></h2> + + + + <table class="bordered"> + <tr> + <th>Module</th> + <th>Status</th> + <th>Notes</th> + </tr> + + <tr> + <td><code><a href="http://java.apache.org/">mod_jserv</a> + </code></td> + <td class="centered">-</td> + <td>JAVA still being ported.</td> + </tr> + + <tr> + <td><code><a href="http://www.php.net/">mod_php3</a></code></td> + <td class="centered">+</td> + <td><code>mod_php3</code> runs fine, with LDAP and GD + and FreeType libraries.</td> + </tr> + + <tr> + <td><code><a href="http://hpwww.ec-lyon.fr/~vincent/apache/mod_put.html">mod_put</a></code></td> + <td class="centered">?</td> + <td>untested</td> + </tr> + + <tr> + <td><code><a href="ftp://hachiman.vidya.com/pub/apache/">mod_session</a></code></td> + <td class="centered">-</td> + <td>untested</td> + </tr> + </table> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/platform/ebcdic.html" title="English"> en </a> | +<a href="../ko/platform/ebcdic.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/ebcdic.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/platform/ebcdic.html.ko.euc-kr new file mode 100644 index 00000000..44526cf8 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/ebcdic.html.ko.euc-kr @@ -0,0 +1,557 @@ +<?xml version="1.0" encoding="EUC-KR"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ko" xml:lang="ko"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>아파치 EBCDIC 포팅 - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>아파치 EBCDIC 포팅</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/platform/ebcdic.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/ebcdic.html" title="Korean"> ko </a></p> +</div> + + + <div class="warning">이 문서는 아파치 웹서버 2.0 버전에서 + 변경된 내용을 담고있지 않다. 아직도 유효한 정보가 있지만, + 주의해서 사용하길 바란다. + </div> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#overview">아파치 EBCDIC 포팅 개요</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#design">설계 목표</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#technical">기술적 해결책</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#porting">포팅에 대해서</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#document">문서 저장에 대해서</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#modules">아파치 모듈의 상태</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#third-party">제삼자가 만든 모듈의 상태</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="overview" id="overview">아파치 EBCDIC 포팅 개요</a></h2> + + + + <p>아파치 웹서버는 1.3 버전때 처음으로 EBCDIC 문자집합을 + 기본 문자집합으로 사용하는 (비-ASCII) 메인플레임 컴퓨터로 + 포팅되었다.</p> + + <p>(<a href="http://www.siemens.de/servers/bs2osd/osdbc_us.htm">BS2000/OSD + 운영체제</a>를 사용하는 SIEMENS 계열 메인플레임을 말한다. + 이 메인플레임 운영체제에는 현재 SVR4계열의 POSIX 하위시스템이 + 있다).</p> + + <p>포팅은 처음에 다음과 같은 목적에서 시작되었다</p> + + <ul> + <li>이 플레폼으로도 <a href="http://dev.apache.org/">아파치 + 웹서버</a>를 포팅할 수 있다는 가능성을 보이기위해서</li> + + <li>(몇년 전에 포팅된) 오래된 <a href="http://www.w3.org/Daemon/">CERN-3.0</a> 서버를 대체할 + "쓸만하고 유능한" 후계자를 찾기위해</li> + + <li>이 플레폼에서 아파치의 prefork 프로세스 방식이 CERN의 + accept-fork-serve 방식 보다 5배 이상 성능이 좋음을 + 보이기위해서.</li> + </ul> + + <p>이 문서는 포팅시 여러 설계상 결정의 이유를 설명한다.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="design" id="design">설계 목표</a></h2> + + + + <p>EBCDIC 포팅의 목적중 하나는 새로운 서버로 전환을 유도하고 + 쉽게 전환할 수 있도록 가능한 (EBCDIC) CERN 서버와 호환성을 + 유지하는 것이다. 그래서 HTML 문서가 (이전 CERN 서버가 인식하는 + 유일한 형식인) ASCII와 (POSIX 하위시스템의 기본 문서 형식. + 그러므로 <code>grep</code>이나 <code>sed</code> 같은 POSIX + 도구를 사용할 수 있는 현실적인 형식인) EBCDIC 중 어느 형식인지 + 설정할 수 있어야 한다. 현재 해결책은 아파치 서버가 중간에서 + 문서를 가로채서 문서의 형식을 파악하는 "가상 MIME 형식"이다 + (아래 참고). 다음 버전에서는 변환해야할 모든 문서에 + "ebcdic-handler"를 정의하는 방법으로 문제를 해결할 것이다.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="technical" id="technical">기술적 해결책</a></h2> + + + + <p>아파치가 BUFF 자료형과 메써드를 사용하여 모든 입출력을 + 하므로 가장 쉬운 방법은 BUFF 처리 함수에 변환기능을 추가하는 + 것이다. 언제든지 변환할 수 있어야 하기때문에 BUFF 객체를 + 변환해야 하는지 알려주는 BUFF 표시를 추가했다. 이 표시는 + HTTP 프로토콜의 여러 단계에서 변경될 수 있다:</p> + + <ul> + <li>요청을 받기 전에 <strong>변환</strong> (요청과 요청헤더가 + 항상 ASCII 형식이기 때문에)</li> + + <li>요청 내용을 받았을때 content type에 따라 + <strong>변환/변환안함</strong> (요청 내용이 ASCII 문자나 + 바이너리 파일인 경우 변환해야 하기때문에)</li> + + <li>응답헤더를 보내기 전에 <strong>변환</strong> (응답헤더는 + 항상 ASCII 형식이기때문에)</li> + + <li>응답 내용을 보낼때 content type에 따라 + <strong>변환/변환안함</strong> (응답 내용이 문자 파일이거나 + 바이너리 파일이기때문에)</li> + </ul> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="porting" id="porting">포팅에 대해서</a></h2> + + + + <ol> + <li> + <p>소스의 변화는 두가지 <code>#ifdef</code>로 구분할 + 수 있다:</p> + + <dl> + <dt><code><strong>#ifdef + CHARSET_EBCDIC</strong></code></dt> + + <dd> + <p>모든 EBCDIC기반 컴퓨터에 필요한 코드. 문자변환, + 두 문자집합간의 연속된 문자값 차이, 어떤 HTTP 프로토콜 + 부분이 변환되야 하는지를 알려주는 표시 <em>등.</em></p> + </dd> + + <dt><code><strong>#ifdef _OSD_POSIX</strong></code></dt> + + <dd> + <p>SIEMENS BS2000/OSD 메인플레임 플레폼에만 필요한 + 코드. BS2000/OSD 플레폼에만 필요한 헤더파일 차이와 + 소켓 구현 문제를 다룬다.</p> + </dd> + </dl> + </li> + + <li> + <p>소켓 수준에서 ASCII와 EBCDIC간 변화는 (BS2000 POSIX에는 + 이 기능을 지원하는 소켓 옵션이 있다) HTTP 프로토콜 수준에서 + 전송되는 자료에 프로토콜관련 문자열과 프로토콜과 무관한 + 일반파일이 섞여있기때문에 의도적으로 사용하지 + <em>않았다</em>. HTTP 프로토콜 문자열은 (<code>GET</code> + 요청, Header: 줄, 기타 정보 <em>등.</em>) 항상 ASCII + 형식이고, 파일전송 부분은 (<em>즉</em>, GIF 그림, CGI + 출력 <em>등.</em>) 서버가 항상 "변환하지않고 그냥" 보내야 + 한다. 서버 코드는 "프로토콜 문자열"과 "일반 자료"를, + 문자열에는 <code>bgets()</code>나 <code>rvputs()</code>, + 바이너리 자료에는 <code>bgets()</code>나 + <code>rvputs()</code> 함수를 사용하여 구별한다. 그러므로 + 무조건 모든 것을 변환하는 것은 적절하지 않다.</p> + + <p>(물론 문자파일의 경우 EBCDIC 문서를 항상 ASCII로 + 서비스하도록 준비해야 한다)</p> + </li> + + <li> + <p>그래서 포팅에는 (컴파일러가 EBCDIC 문자열로 변환한) + 서버 내부 문자열과 서버가 생성한 문서를 기본 프로토콜 + 수준에서 변환하는 기능이 있다. 서버 코드에 산재된 ASCII + escape문자 <code>\012</code>와 <code>\015</code>는 예외다: + 이들이 이미 ASCII <code>\n</code>과 <code>\r</code>의 + 바이너리 값이기때문에 ASCII로 두번 변환하면 안된다. + 이 예외는 서버가 생성한 문자열에만 적용된다; <em>외부</em> + EBCDIC 문서는 ASCII 줄바꿈문자를 포함하면 안된다.</p> + </li> + + <li> + <p>BUFF 관리함수를 사용하는 방법을 살펴본 후 나는 모든 + puts/write/get/gets가 거치게되는 "ebcdic/ascii 변환 + 계층"을 추가하고, 동적으로 변환유무를 설정할 수 있는 + 변환 표시를 추가했다. 문서가 원본(파일이나 CGI 출력)에서 + 대상(요청한 클라이언트)으로 이동할때 항상 이 계층을 + 두번 지난다: <code>파일 -> 아파치</code>, <code>아파치 + -> 클라이언트</code>.</p> + + <p>서버는 이제 EBCDIC 형식으로 된 CGI 스크립트 출력의 + 헤더줄을 읽고, 나머지 스크립트 출력이 ASCII임을 알아낼 + 수 있다 (WWW 방문자수를 세는 프로그램과 같은 경우: 문서 + 내용은 GIF 그림이다). 기본 EBCDIC 형식으로 모든 헤더를 + 처리한다; 그런 다음 서비스할 문서의 type에 따라 서버는 + 문서 내용이 이미 ASCII인지 혹은 EBCDIC에서 변환을 해야 + 하는지 결정한다.</p> + </li> + + <li> + <p>(MIME type이 text/plain, text/html <em>등</em>) 내용이 + 일반 문자인 문서를 암묵적으로 ASCII로 변환하거나, (사용자에게 + 빠르게 서비스하기위해 미리 문서를 ASCII 형식으로 저장하였거나 + NFS로 마운트한 디렉토리에 파일이 있는 경우) 변환없이 + 서비스할 수 있다.</p> + + <p><strong>예:</strong></p> + + <p>이름이 <code>.ahtml</code>로 끝나는 파일을 암묵적인 + 변환없이 ASCII <code>text/html</code> 문서로 (그리고 + <code>.ascii</code> 확장자는 ASCII + <code>text/plain</code>으로) 서비스하려면 다음 지시어를 + 사용한다:</p> + + <div class="example"><p><code> + AddType text/x-ascii-html .ahtml <br /> + AddType text/x-ascii-plain .ascii + </code></p></div> + + <p>또, <code>text/foo</code> 식의 MIME type을 + <code>AddType</code> "<code>text/x-ascii-foo</code>" + 설정하여 "일반 ASCII"로 서비스할 수 있다.</p> + </li> + + <li> + <p>내용이 일반 문자가 아닌 문서는 변환없이 항상 "바이너리"로 + 서비스한다. <em>예를 들어</em>, GIF/ZIP/AU 파일형식에 + 가장 적합한 선택이다. 물론 사용자는 "<code>rcp -b</code>" + 바이너리 옵션을 사용하여 파일을 메인플레임 호스트로 + 복사했어야 한다.</p> + </li> + + <li> + <p>서버파싱 파일은 항상 컴퓨터가 사용하는 기본 형식으로 + (<em>즉</em>, EBCDIC) 저장되었다고 가정하고, 처리후에 + 변환한다.</p> + </li> + + <li> + <p>CGI 출력의 경우 CGI 스크립트가 변환이 필요한지 결정한다: + 적절한 Content-Type을 설정하여, 문자파일은 변환하고, + GIF 출력은 변환없이 보낼 수 있다. 우리가 포팅한 wwwcount + 프로그램이 후자의 경우다.</p> + </li> + + </ol> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="document" id="document">문서 저장에 대해서</a></h2> + + + + <h3><a name="binary" id="binary">바이너리 파일</a></h3> + + + + <p>서버는 <code>Content-Type:</code>이 <code>text/</code>로 + 시작하는 않는 파일을 <em>바이너리 파일</em>로 간주하여 + 어떤 변환도 하지 않는다. 바이너리 파일에는 GIF 그림, gzip으로 + 압축한 파일 등이 있다.</p> + + <p>메인플레임 호스트와 유닉스 혹은 윈도우즈 PC간에 바이너리 + 파일을 전송할 때는 ftp "binary" (<code>TYPE I</code>) 명령어나 + 메인플레임 호스트에서 (유닉스 <code>rcp</code>는 + <code>-b</code> 옵션을 지원하지 않는다) <code>rcp -b</code> + 명령어를 반드시 사용하라.</p> + + + + <h3><a name="text" id="text">문자 문서</a></h3> + + + + <p>기본적으로 서버는 문자파일이 (<em>즉</em>, + <code>Content-Type:</code>이 <code>text/</code>로 시작하는 + 모든 파일) 호스트의 기본 문자집합인 EBCDIC으로 저장되었다고 + 가정한다.</p> + + + + <h3><a name="ssi" id="ssi">Server Side Include 문서</a></h3> + + + + <p>SSI 문서는 현재 EBCDIC 형식으로만 저장해야 한다. 처리하기 + 전에 ASCII를 변환하지 않는다.</p> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="modules" id="modules">아파치 모듈의 상태</a></h2> + + + + <table class="bordered"> + <tr> + <th>모듈</th> + <th>상태</th> + <th>비고</th> + </tr> + + <tr> + <td><code class="module"><a href="../mod/core.html">core</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_access.html">mod_access</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_actions.html">mod_actions</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_asis.html">mod_asis</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_auth.html">mod_auth</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_auth_anon.html">mod_auth_anon</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_auth_dbm.html">mod_auth_dbm</a></code></td> + <td class="centered">?</td> + <td>자체 <code>libdb.a</code>를 사용하여</td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_autoindex.html">mod_autoindex</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_cern_meta.html">mod_cern_meta</a></code></td> + <td class="centered">?</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code>mod_digest</code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_so.html">mod_so</a></code></td> + <td class="centered">-</td> + <td>공유라이브러리가 없음</td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_env.html">mod_env</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_example.html">mod_example</a></code></td> + <td class="centered">-</td> + <td>(시험 단계)</td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_expires.html">mod_expires</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_headers.html">mod_headers</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_imap.html">mod_imap</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_info.html">mod_info</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code>mod_log_agent</code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code>mod_log_referer</code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_mime_magic.html">mod_mime_magic</a></code></td> + <td class="centered">?</td> + <td>아직 포팅안됨</td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_negotiation.html">mod_negotiation</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code></td> + <td class="centered">+</td> + <td>테스트안됨</td> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_setenvif.html">mod_setenvif</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_speling.html">mod_speling</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_status.html">mod_status</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_unique_id.html">mod_unique_id</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_userdir.html">mod_userdir</a></code></td> + <td class="centered">+</td> + <td /> + </tr> + + <tr> + <td><code class="module"><a href="../mod/mod_usertrack.html">mod_usertrack</a></code></td> + <td class="centered">?</td> + <td>테스트안됨</td> + </tr> + </table> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="third-party" id="third-party">제삼자가 만든 모듈의 상태</a></h2> + + + + <table class="bordered"> + <tr> + <th>모듈</th> + <th>상태</th> + <th>비고</th> + </tr> + + <tr> + <td><code><a href="http://java.apache.org/">mod_jserv</a> + </code></td> + <td class="centered">-</td> + <td>JAVA는 포팅중이다.</td> + </tr> + + <tr> + <td><code><a href="http://www.php.net/">mod_php3</a></code></td> + <td class="centered">+</td> + <td><code>mod_php3</code>는 LDAP, GD, FreeType 라이브러리와 + 함께 잘 동작한다.</td> + </tr> + + <tr> + <td><code><a href="http://hpwww.ec-lyon.fr/~vincent/apache/mod_put.html">mod_put</a></code></td> + <td class="centered">?</td> + <td>테스트안됨</td> + </tr> + + <tr> + <td><code><a href="ftp://hachiman.vidya.com/pub/apache/">mod_session</a></code></td> + <td class="centered">-</td> + <td>테스트안됨</td> + </tr> + </table> + + </div></div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/platform/ebcdic.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/ebcdic.html" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/index.html b/rubbos/app/httpd-2.0.64/docs/manual/platform/index.html new file mode 100644 index 00000000..df57cd0f --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/index.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/index.html.en b/rubbos/app/httpd-2.0.64/docs/manual/platform/index.html.en new file mode 100644 index 00000000..a8870ebf --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/index.html.en @@ -0,0 +1,94 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Platform Specific Notes - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="../"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a></div><div id="page-content"><div id="preamble"><h1>Platform Specific Notes</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/platform/" title="English"> en </a> | +<a href="../ko/platform/" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#win">Microsoft Windows</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#other">Other Platforms</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="win" id="win">Microsoft Windows</a></h2> + + + + <dl> + <dt>Using Apache</dt> + <dd> + <p>This document explains how to install, configure and run Apache 2.0 + under Microsoft Windows.</p> + + <p>See: <a href="windows.html">Using Apache with Microsoft Windows</a></p> + </dd> + </dl> + + <dl> + <dt>Compiling Apache</dt> + <dd> + <p>There are many important points before you begin compiling Apache. + This document explain them.</p> + + <p>See: <a href="win_compiling.html">Compiling Apache for Microsoft Windows</a></p> + </dd> + </dl> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="other" id="other">Other Platforms</a></h2> + + + + <dl> + <dt>Novell NetWare</dt> + <dd> + <p>This document explains how to install, configure and run Apache 2.0 + under Novell NetWare 5.1 and above.</p> + + <p>See: <a href="netware.html">Using Apache With Novell NetWare</a></p> + </dd> + </dl> + + <dl> + <dt>EBCDIC</dt> + <dd> + <p>Version 1.3 of the Apache HTTP Server is the first version which + includes a port to a (non-ASCII) mainframe machine which uses the + EBCDIC character set as its native codeset.</p> + + <div class="warning"><strong>Warning:</strong> This document + has not been updated to take into account changes made in + the 2.0 version of the Apache HTTP Server. Some of the + information may still be relevant, but please use it + with care.</div> + + <p>See: <a href="ebcdic.html">The Apache EBCDIC Port</a></p> + </dd> + </dl> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/platform/" title="English"> en </a> | +<a href="../ko/platform/" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/index.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/platform/index.html.ko.euc-kr new file mode 100644 index 00000000..0486d8fb --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/index.html.ko.euc-kr @@ -0,0 +1,94 @@ +<?xml version="1.0" encoding="EUC-KR"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ko" xml:lang="ko"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>플래폼별 설명 - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="../"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a></div><div id="page-content"><div id="preamble"><h1>플래폼별 설명</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/platform/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/" title="Korean"> ko </a></p> +</div> +</div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#win">Microsoft Windows</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#other">기타 플래폼</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="win" id="win">Microsoft Windows</a></h2> + + + + <dl> + <dt>아파치 사용법</dt> + <dd> + <p>이 문서는 Microsoft Windows에서 아파치 2.0을 설치, + 설정, 실행하는 방법을 설명한다.</p> + + <p>문서: <a href="windows.html">Microsoft Windows에서 + 아파치 사용법</a></p> + </dd> + </dl> + + <dl> + <dt>아파치 컴파일</dt> + <dd> + <p>아파치를 컴파일하기 전에 주의할 점이 많다. 이 문서는 + 이점을 설명한다.</p> + + <p>문서: <a href="win_compiling.html">Microsoft Windows용 아파치 컴파일</a></p> + </dd> + </dl> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="other" id="other">기타 플래폼</a></h2> + + + + <dl> + <dt>Novell NetWare</dt> + <dd> + <p>이 문서는 Novell NetWare 5.1 이상에서 아파치 2.0을 + 설치, 설정, 실행하는 방법을 설명한다.</p> + + <p>문서: <a href="netware.html">Novell NetWare에서 아파치 + 사용하기</a></p> + </dd> + </dl> + + <dl> + <dt>EBCDIC</dt> + <dd> + <p>아파치 웹서버는 1.3 버전때 처음으로 EBCDIC 문자집합을 + 기본 문자집합으로 사용하는 (비-ASCII) 메인플레임 컴퓨터로 + 포팅되었다.</p> + + <div class="warning"><strong>경고:</strong> 이 문서는 + 아파치 웹서버 2.0 버전에서 변경된 내용을 담고있지 않다. + 아직도 유효한 정보가 있지만, 주의해서 사용하길 바란다.</div> + + <p>문서: <a href="ebcdic.html">아파치 EBCDIC 포팅</a></p> + </dd> + </dl> + + </div></div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/platform/" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/netware.html b/rubbos/app/httpd-2.0.64/docs/manual/platform/netware.html new file mode 100644 index 00000000..953689aa --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/netware.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: netware.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: netware.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/netware.html.en b/rubbos/app/httpd-2.0.64/docs/manual/platform/netware.html.en new file mode 100644 index 00000000..b304f348 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/netware.html.en @@ -0,0 +1,589 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Using Apache With Novell NetWare - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Using Apache With Novell NetWare</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/platform/netware.html" title="English"> en </a> | +<a href="../ko/platform/netware.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div> + + + <p>This document explains how to install, configure and run + Apache 2.0 under Novell NetWare 6.0 and above. If you find any bugs, + or wish to contribute in other ways, please use our + <a href="http://httpd.apache.org/bug_report.html">bug reporting + page.</a></p> + + <p>The bug reporting page and dev-httpd mailing list are <em>not</em> + provided to answer questions about configuration or running Apache. + Before you submit a bug report or request, first consult this document, the + <a href="../faq/">Frequently Asked Questions</a> page and the other + relevant documentation topics. If you still have a question or problem, + post it to the <a href="news://developer-forums.novell.com/novell.devsup.webserver"> + novell.devsup.webserver</a> newsgroup, where many Apache users are more than + willing to answer new and obscure questions about using Apache on NetWare.</p> + + <p>Most of this document assumes that you are installing Apache + from a binary distribution. If you want to compile Apache + yourself (possibly to help with development, or to track down + bugs), see the section on <a href="#comp">Compiling Apache for + NetWare</a> below.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Requirements</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for NetWare</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#inst">Installing Apache for NetWare</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#run">Running Apache for NetWare</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#use">Configuring Apache for NetWare</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#comp">Compiling Apache for NetWare</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="req" id="req">Requirements</a></h2> + + + + <p>Apache 2.0 is designed to run on NetWare 6.0 service pack 3 + and above. If you are running a service pack less + than SP3, you must install the latest + <a href="http://developer.novell.com/ndk/libc.htm">NetWare Libraries + for C (LibC)</a>.</p> + + <p>NetWare service packs are available <a href="http://support.novell.com/misc/patlst.htm#nw">here</a>.</p> + + <p>Apache 2.0 for NetWare can also be run in a NetWare 5.1 environment + as long as the latest service pack or the latest version + of the <a href="http://developer.novell.com/ndk/libc.htm">NetWare Libraries + for C (LibC)</a> has been installed . <strong>WARNING:</strong> Apache 2.0 + for NetWare has not been targeted for or tested in this environment.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="down" id="down">Downloading Apache for NetWare</a></h2> + + + + <p>Information on the latest version of Apache can be found on + the Apache web server at <a href="http://www.apache.org/">http://www.apache.org/</a>. This + will list the current release, any more recent alpha or + beta-test releases, together with details of mirror web and + anonymous ftp sites. Binary builds of the latest releases of + Apache 2.0 for NetWare can be downloaded from + <a href="http://www.apache.org/dist/httpd/binaries/netware">here</a>.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="inst" id="inst">Installing Apache for NetWare</a></h2> + + + + <p>There is no Apache install program for NetWare currently. If you + are building Apache 2.0 for NetWare from source, you will need to + copy the files over to the server manually.</p> + + <p>Follow these steps to install Apache on NetWare from the + binary download (assuming you will install to + <code>sys:/apache2</code>):</p> + + <ul> + <li>Unzip the binary download file to the root of the <code>SYS:</code> + volume (may be installed to any volume)</li> + + <li>Edit the <code>httpd.conf</code> file setting <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> and <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> along with any file path values + to reflect your correct server settings</li> + + <li>Add <code>SYS:/APACHE2</code> to the search path, for example: + <div class="example"><p><code>SEARCH ADD SYS:\APACHE2</code></p></div> + </li> + + </ul> + + <p>Follow these steps to install Apache on NetWare manually + from your own build source (assuming you will install to + <code>sys:/apache2</code>):</p> + + <ul> + <li>Create a directory called <code>Apache2</code> on a + NetWare volume</li> + + <li>Copy <code>APACHE2.NLM</code>, <code>APRLIB.NLM</code> + to <code>SYS:/APACHE2</code></li> + + <li>Create a directory under <code>SYS:/APACHE2</code> + called <code>BIN</code></li> + + <li>Copy <code>HTDIGEST.NLM</code>, <code>HTPASSWD.NLM</code>, + <code>HTDBM.NLM</code>, <code>LOGRES.NLM</code>, <code>ROTLOGS.NLM</code> + to <code>SYS:/APACHE2/BIN</code></li> + + <li>Create a directory under <code>SYS:/APACHE2</code> + called <code>CONF</code></li> + + <li>Copy the <code>HTTPD-STD.CONF</code> file to the + <code>SYS:/APACHE2/CONF</code> directory and rename to + <code>HTTPD.CONF</code></li> + + <li>Copy the <code>MIME.TYPES</code>, <code>CHARSET.CONV</code> and + <code>MAGIC</code> files to <code>SYS:/APACHE2/CONF</code> directory</li> + + <li>Copy all files and subdirectories in <code>\HTTPD-2.0\DOCS\ICONS</code> + to <code>SYS:/APACHE2/ICONS</code></li> + + <li>Copy all files and subdirectories in <code>\HTTPD-2.0\DOCS\MANUAL</code> + to <code>SYS:/APACHE2/MANUAL</code></li> + + <li>Copy all files and subdirectories in <code>\HTTPD-2.0\DOCS\ERROR</code> + to <code>SYS:/APACHE2/ERROR</code></li> + + <li>Copy all files and subdirectories in <code>\HTTPD-2.0\DOCS\DOCROOT</code> + to <code>SYS:/APACHE2/HTDOCS</code></li> + + <li>Create the directory <code>SYS:/APACHE2/LOGS</code> + on the server</li> + + <li>Create the directory <code>SYS:/APACHE2/CGI-BIN</code> + on the server</li> + + <li>Create the directory <code>SYS:/APACHE2/MODULES</code> + and copy all nlm modules into the <code>modules</code> directory</li> + + <li>Edit the <code>HTTPD.CONF</code> file searching for all + <code>@@Value@@</code> markers and replacing them with the + appropriate setting</li> + + <li>Add <code>SYS:/APACHE2</code> to the search path, for example: + <div class="example"><p><code>SEARCH ADD SYS:\APACHE2</code></p></div> + </li> + </ul> + + <p>Apache may be installed to other volumes besides the default <code>SYS</code> volume.</p> + + <p>During the build process, adding the keyword "install" to the makefile command line + will automatically produce a complete distribution package under the subdirectory + <code>DIST</code>. Install Apache by simply copying the distribution that was produced + by the makfiles to the root of a NetWare volume (see: <a href="#comp">Compiling Apache for + NetWare</a> below).</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="run" id="run">Running Apache for NetWare</a></h2> + + + + <p>To start Apache just type <code>apache</code> at the + console. This will load apache in the OS address space. If you + prefer to load Apache in a protected address space you may + specify the address space with the load statement as follows:</p> + + <div class="example"><p><code> + load address space = apache2 apache2 + </code></p></div> + + <p>This will load Apache into an address space called apache2. + Running multiple instances of Apache concurrently on NetWare is + possible by loading each instance into its own protected + address space.</p> + + <p>After starting Apache, it will be listening to port 80 + (unless you changed the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> + directive in the configuration files). + To connect to the server and access the default page, + launch a browser and enter the server's name or address. This + should respond with a welcome page, and a link to the Apache + manual. If nothing happens or you get an error, look in the + <code>error_log</code> file in the <code>logs</code> + directory.</p> + + <p>Once your basic installation is working, you should + configure it properly by editing the files in the + <code>conf</code> directory.</p> + + <p>To unload Apache running in the OS address space just type + the following at the console:</p> + + <div class="example"><p><code> + unload apache2 + </code></p></div> + + <p>or</p> + + <div class="example"><p><code> + apache2 shutdown + </code></p></div> + + <p>If apache is running in a protected address space specify the + address space in the unload statement:</p> + + <div class="example"><p><code> + unload address space = apache2 apache2 + </code></p></div> + + <p>When working with Apache it is important to know how it will + find the configuration files. You can specify a configuration + file on the command line in two ways:</p> + + <ul> + <li><code>-f</code> specifies a path to a particular + configuration file</li> + </ul> + + <div class="example"><p><code> + apache2 -f "vol:/my server/conf/my.conf" + </code></p></div> + + <div class="example"><p><code> + apache -f test/test.conf + </code></p></div> + + <p>In these cases, the proper <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> + should be set in the configuration file.</p> + + <p>If you don't specify a configuration file name with <code>-f</code>, + Apache will use the file name compiled into the server, usually + <code>conf/httpd.conf</code>. Invoking Apache with the <code>-V</code> + switch will display this value labeled as <code>SERVER_CONFIG_FILE</code>. + Apache will then determine its <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> + by trying the following, in this order:</p> + + <ul> + <li>A <code>ServerRoot</code> directive via a + <code>-C</code> switch.</li> + + <li>The <code>-d</code> switch on the command line.</li> + + <li>Current working directory</li> + + <li>The server root compiled into the server.</li> + </ul> + + <p>The server root compiled into the server is usually <code>sys:/apache2</code>. + invoking apache with the <code>-V</code> switch will display this value labeled as + <code>HTTPD_ROOT</code>.</p> + + <p>Apache 2.0 for NetWare includes a set of command line directives that can + be used to modify or display information about the running instance of the + web server. These directives are only available while Apache is running. Each + of these directives must be preceded by the keyword <code>APACHE2</code>.</p> + + <dl> + <dt>RESTART</dt> + <dd>Instructs Apache to terminate all running worker + threads as they become idle, reread the configuration file and restart each + worker thread based on the new configuration.</dd> + + <dt>VERSION</dt> + <dd>Displays version information about the currently + running instance of Apache.</dd> + + <dt>MODULES</dt> + <dd>Displays a list of loaded modules both built-in + and external.</dd> + + <dt>DIRECTIVES</dt> + <dd>Displays a list of all available directives.</dd> + + <dt>SETTINGS</dt> + <dd>Enables or disables the thread status display + on the console. When enabled, the state of each running threads is displayed + on the Apache console screen.</dd> + + <dt>SHUTDOWN</dt> + <dd>Terminates the running instance of the Apache + web server.</dd> + + <dt>HELP</dt> + <dd>Describes each of the runtime directives.</dd> + </dl> + + <p>By default these directives are issued against the instance of Apache running + in the OS address space. To issue a directive against a specific instance running + in a protected address space, include the -p parameter along with the name of the + address space. For more information type "apache2 Help" on the command line.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="use" id="use">Configuring Apache for NetWare</a></h2> + + + + <p>Apache is configured by reading configuration files usually stored + in the <code>conf</code> directory. These are the same as files used + to configure the Unix version, but there are a few different directives for + Apache on NetWare. See the <a href="../">Apache + documentation</a> for all the available directives.</p> + + <p>The main differences in Apache for NetWare are:</p> + + <ul> + <li> + <p>Because Apache for NetWare is multithreaded, it does not + use a separate process for each request, as Apache does on some Unix + implementations. Instead there are only threads running: a parent + thread, and multiple child or worker threads which handle the requests.</p> + + <p>Therefore the "process"-management directives are different:</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code> - + Like the Unix directive, this controls how many requests + a worker thread will serve before exiting. The recommended default, + <code>MaxRequestsPerChild 0</code>, causes the thread to continue servicing + request indefinitely. It is recommended on NetWare, unless there is some + specific reason, that this directive always remain set to <code>0</code>.</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#startthreads">StartThreads</a></code> - + This directive tells the server how many threads it should start initially. + The recommended default is <code>StartThreads 50</code>.</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#minsparethreads">MinSpareThreads</a></code> - + This directive instructs the server to spawn additional worker threads + if the number of idle threads ever falls below this value. The recommended + default is <code>MinSpareThreads 10</code>.</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#maxsparethreads">MaxSpareThreads</a></code> - + This directive instructs the server to begin terminating worker threads + if the number of idle threads ever exceeds this value. The recommended + default is <code>MaxSpareThreads 100</code>.</p> + + <p><code class="directive"><a href="../mod/mpm_netware.html#maxthreads">MaxThreads</a></code> - + This directive limits the total number of work threads to a maximum + value. The recommended default is <code>ThreadsPerChild 250</code>.</p> + + <p><code class="directive"><a href="../mod/mpm_netware.html#threadstacksize">ThreadStackSize</a></code> - + This directive tells the server what size of stack to use + for the individual worker thread. The recommended default + is <code>ThreadStackSize 65536</code>.</p> + </li> + + <li> + <p>The directives that accept filenames as arguments must use + NetWare filenames instead of Unix names. However, because Apache + uses Unix-style names internally, forward slashes must be used + rather than backslashes. It is recommended that all rooted file paths + begin with a volume name. If omitted, Apache will assume the + <code>SYS:</code> volume which may not be correct.</p> + </li> + + <li> + <p>Apache for NetWare has the ability to load modules at + runtime, without recompiling the server. If Apache is + compiled normally, it will install a number of optional + modules in the <code>\Apache2\modules</code> directory. + To activate these, or other modules, the <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code> directive + must be used. For example, to active the status module, use + the following:</p> + + <div class="example"><p><code> + LoadModule status_module modules/status.nlm + </code></p></div> + + <p>Information on <a href="../mod/mod_so.html#creating">creating loadable + modules</a> is also available.</p> + </li> + </ul> + + <h3><a name="use-add" id="use-add">Additional NetWare specific directives:</a></h3> + + + + <ul> + <li><code class="directive"><a href="../mod/core.html#cgimapextension">CGIMapExtension</a></code> - + This directive maps a CGI file extension to a script interpreter.</li> + </ul> + <ul> + <li><code class="directive"><a href="../mod/mod_nw_ssl.html#securelisten">SecureListen</a></code> - + Enables SSL encryption for a specified port.</li> + </ul> + <ul> + <li><code class="directive"><a href="../mod/mod_nw_ssl.html#nwssltrustedcerts">NWSSLTrustedCerts</a></code> - + Adds trusted certificates that are used to create secure connections to proxied servers.</li> + </ul> + <ul> + <li><code class="directive"><a href="../mod/mod_nw_ssl.html#nwsslupgradeable">NWSSLUpgradeable</a></code> - + Allow a connection created on the specified address/port to be upgraded to an SSL connection.</li> + </ul> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="comp" id="comp">Compiling Apache for NetWare</a></h2> + + + + <p>Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once + Apache has been built, it can be installed to the root of any NetWare + volume. The default is the <code>sys:/Apache2</code> directory.</p> + + <p>Before running the server you must fill out the <code>conf</code> + directory. Copy the file <code>HTTPD-STD.CONF</code> from the distribution + <code>conf</code> directory and rename it to <code>HTTPD.CONF</code>. + Edit the <code>HTTPD.CONF</code> file searching for all <code>@@Value@@</code> + markers and replacing them with the appropriate setting. Copy over + the <code>conf/magic</code> and <code>conf/mime.types</code> files as well. + Alternatively, a complete distribution can be built by including the keyword + <code>install</code> when invoking the makefiles.</p> + + <h3><a name="comp-req" id="comp-req">Requirements:</a></h3> + + + + <p>The following development tools are required to build + Apache 2.0 for NetWare:</p> + + <ul> + <li>Metrowerks CodeWarrior 6.0 or higher with the + <a href="http://developer.novell.com/ndk/cwpdk.htm">NetWare PDK 3.0</a> + or higher.</li> + + <li><a href="http://developer.novell.com/ndk/libc.htm">NetWare Libraries + for C (LibC)</a></li> + + <li><a href="http://developer.novell.com/ndk/cldap.htm">LDAP Libraries + for C</a></li> + + <li><a href="http://www.gzip.org/zlib/">ZLIB Compression Library source code</a></li> + + <li>AWK utility (awk, gawk or similar). AWK can be downloaded from + <a href="http://developer.novell.com/ndk/apache.htm">http://developer.novell.com/ndk/apache.htm</a>. + The utility must be found in your windows path and must be named <code>awk.exe</code>.</li> + + <li>To build using the makefiles, you will need GNU make version 3.78.1 (GMake) available at + <a href="http://developer.novell.com/ndk/apache.htm">http://developer.novell.com/ndk/apache.htm</a>.</li> + </ul> + + + + <h3><a name="comp-make" id="comp-make">Building Apache using the NetWare makefiles:</a></h3> + + + + <ul> + <li>Set the environment variable <code>NOVELLLIBC</code> to the + location of the NetWare Libraries for C SDK, for example: + <div class="example"><p><code>Set NOVELLLIBC=c:\novell\ndk\libc</code></p></div> + </li> + + <li>Set the environment variable <code>METROWERKS</code> to the + location where you installed the Metrowerks CodeWarrior compiler, + for example: + <div class="example"><p><code>Set METROWERKS=C:\Program Files\Metrowerks\CodeWarrior</code></p></div> + If you installed to the default location <code>C:\Program + Files\Metrowerks\CodeWarrior</code>, you don't need to set this.</li> + + <li>Set the environment variable <code>LDAPSDK</code> to the + location where you installed the LDAP Libraries for C, for example: + <div class="example"><p><code>Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc</code></p></div> + </li> + + <li>Set the environment variable <code>ZLIBSDK</code> to the + location where you installed the source code for the ZLib Library, + for example: + <div class="example"><p><code>Set ZLIBSDK=D:\NOVELL\zlib</code></p></div> + </li> + + <li>Set the environment variable <code>AP_WORK</code> to the full path of + the <code>\httpd-2.0</code> directory.</li> + + <li>Set the environment variable <code>APR_WORK</code> to the full path of + the <code>\httpd-2.0\srclib\apr</code> directory.</li> + + <li>Make sure that the path to the AWK utility and the GNU make utility + (<code>gmake.exe</code>) have been included in the system's + <code>PATH</code> environment variable.</li> + + <li>Download the source code and unzip to an appropriate directory on + your workstation.</li> + + <li>Change directory to <code>\httpd-2.0\srclib\apr-util\uri</code> and build + <code>GENURI.nlm</code> by running "<code>gmake -f nwgnumakefile</code>".</li> + + <li>Copy the file <code>GENURI.nlm</code> to the <code>SYS:</code> volume + of a NetWare server and run using the following command: + <div class="example"><p><code>SYS:\genuri > sys:\uri_delims.h</code></p></div> + </li> + + <li>Copy the file <code>uri_delims.h</code> to the directory + <code>\httpd-2.0\srclib\apr-util\uri</code> on the build machine.</li> + + <li>Change directory to <code>\httpd-2.0\srclib\apr</code> and build APR + by running "<code>gmake -f nwgnumakefile</code>"</li> + + <li>Change directory to <code>\httpd-2.0\srclib\pcre</code> and build + <code>DFTABLES.nlm</code> by running "<code>gmake -f nwgnumakefile</code>"</li> + + <li>Change directory to <code>\httpd-2.0\server</code> and build + <code>GENCHARS.nlm</code> by running "<code>gmake -f nwgnumakefile</code>"</li> + + <li>Copy the files <code>GENCHARS.nlm</code> and <code>DFTABLES.nlm</code> + from their respective directories to the <code>SYS:</code> volume of a + NetWare server and run them using the following commands: + <div class="example"><p><code> + SYS:\genchars > sys:\test_char.h<br /> + SYS:\dftables > sys:\chartables.c<br /> + </code></p></div> + </li> + + <li>Copy the files <code>test_char.h</code> and <code>chartables.c</code> + to the directory <code>\httpd-2.0\os\netware</code> on the build machine.</li> + + <li>Change directory to <code>\httpd-2.0</code> and build Apache by running + "<code>gmake -f nwgnumakefile</code>". You can create a distribution directory by + adding an install parameter to the command, for example: + <div class="example"><p><code>gmake -f nwgnumakefile install</code></p></div> + </li> + </ul> + + + + <h3><a name="comp-add" id="comp-add">Additional make options</a></h3> + + + + <ul> + <li><code>gmake -f nwgnumakefile</code><p>Builds release versions of all of the + binaries and copies them to a <code>\release</code> destination directory.</p></li> + + <li><code>gmake -f nwgnumakefile DEBUG=1</code><p>Builds debug versions of all of the + binaries and copies them to a <code>\debug</code> destination directory.</p></li> + + <li><code>gmake -f nwgnumakefile install</code><p>Creates a complete Apache + distribution with binaries, docs and additional support files in a + <code>\dist\Apache2</code> directory.</p></li> + + <li><code>gmake -f nwgnumakefile installdev</code><p>Same as install but also creates a + <code>\lib</code> and <code>\include</code> directory in the destination directory + and copies headers and import files.</p></li> + + <li><code>gmake -f nwgnumakefile clean</code><p>Cleans all object files and binaries + from the <code>\release</code> or <code>\debug</code> build areas depending on whether + <code>DEBUG</code> has been defined.</p></li> + + <li><code>gmake -f nwgnumakefile clobber_all</code><p>Same as clean and also deletes + the distribution directory if it exists.</p></li> + </ul> + + + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/platform/netware.html" title="English"> en </a> | +<a href="../ko/platform/netware.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/netware.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/platform/netware.html.ko.euc-kr new file mode 100644 index 00000000..fa57fc44 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/netware.html.ko.euc-kr @@ -0,0 +1,579 @@ +<?xml version="1.0" encoding="EUC-KR"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ko" xml:lang="ko"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Novell NetWare에서 아파치 사용하기 - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Novell NetWare에서 아파치 사용하기</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/platform/netware.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/netware.html" title="Korean"> ko </a></p> +</div> + + + <p>이 문서는 Novell NetWare 6.0 이상에서 아파치 2.0을 설치, + 설정, 실행하는 방법을 설명한다. 버그를 찾았거나 다른 방법으로 + 돕고싶다면, <a href="http://httpd.apache.org/bug_report.html">버그 + 보고 페이지</a>를 이용하길 바란다.</p> + + <p>버그 보고 페이지나 dev-httpd 메일링리스트는 아파치 설정과 + 실행에 대한 질문을 답하지 <em>않는다</em>. 버그를 보고하기 + 전에 먼저 이 문서와 <a href="../faq/">자주 물어보는 질문 + (FAQ)</a> 페이지, 다른 관련문서를 살펴봐라. 그래도 궁금한 + 점이나 문제가 있다면, NetWare에서 아파치 사용에 대한 어렵고 + 새로운 질문을 답해줄 많은 아파치 사용자가 있는 <a href="news://developer-forums.novell.com/novell.devsup.webserver"> + novell.devsup.webserver</a> 뉴스그룹에 글을 올리길 바란다.</p> + + <p>이 문서는 바이너리 배포본으로 아파치를 설치했다고 가정한다. + (아마도 개발에 도움을 주거나 버그를 찾기위해) 직접 아파치를 + 컴파일하려면 아래 <a href="#comp">NetWare에서 아파치 + 컴파일하기</a> 절을 참고하라.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">요구조건</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#down">NetWare용 아파치 다운받기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#inst">NetWare용 아파치 설치하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#run">NetWare용 아파치 실행하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#use">NetWare용 아파치 설정하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#comp">Netware용 아파치 컴파일하기</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="req" id="req">요구조건</a></h2> + + + + <p>아파치 2.0은 NetWare 6.0 service pack 3 이상에서 동작하도록 + 설계되었다. SP3보다 낮은 service pack을 사용한다면 최신 + <a href="http://developer.novell.com/ndk/libc.htm">NetWare + Libraries for C (LibC)</a>를 설치해야 한다.</p> + + <p>NetWare service pack은 <a href="http://support.novell.com/misc/patlst.htm#nw">여기</a>에 + 있다.</p> + + <p>최신 service pack이나 최신 버전 <a href="http://developer.novell.com/ndk/libc.htm">NetWare + Libraries for C (LibC)</a>를 설치했다면 NetWare 5.1 환경에서도 + NetWare용 아파치 2.0을 실행할 수 있다. <strong>경고:</strong> + NetWare용 아파치 2.0은 이 환경을 고려하지 않았고 테스트하지 + 않았다.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="down" id="down">NetWare용 아파치 다운받기</a></h2> + + + + <p>아파치 최신 버전에 대한 정보는 <a href="http://www.apache.org/">http://www.apache.org/</a>에서 + (아파치 웹서버) 찾을 수 있다. 여기에는 현재 버전과 최근 + 알파/베타테스트 버전, 미러 웹사이트와 ftp 사이트 정보가 + 있다. NetWare용 아파치 2.0의 최신 바이너리 배포본은 <a href="http://www.apache.org/dist/httpd/binaries/netware">여기</a>에서 + 다운받을 수 있다.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="inst" id="inst">NetWare용 아파치 설치하기</a></h2> + + + + <p>현재 NetWare용 아파치 설치프로그램은 없다. NetWare용 + 아파치 2.0 소스를 직접 컴파일한다면 파일을 서버로 직접 + 복사해줘야 한다.</p> + + <p>바이너리로 다운받은 NetWare용 아파치를 설치하는 과정은 + 다음과 같다 (<code>sys:/apache2</code>에 설치한다고 가정한다):</p> + + <ul> + <li>바이너리로 다운받은 압축파일을 <code>SYS:</code> 볼륨 + 최상위 디렉토리에 푼다 (다른 볼륨에 설치해도 된다)</li> + + <li><code>httpd.conf</code> 파일을 수정하여 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>와 <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>과 파일경로 값을 서버에 + 알맞게 지정한다</li> + + <li>예를 들어 <div class="example"><p><code>SEARCH ADD SYS:\APACHE2</code></p></div>와 + 같이 검색경로에 <code>SYS:/APACHE2</code>를 추가한다 + </li> + + </ul> + + <p>직접 소스를 컴파일한 경우 NetWare에 아파치를 설치하는 + 방법은 다음과 같다 (<code>sys:/apache2</code>에 설치한다고 + 가정한다):</p> + + <ul> + <li>NetWare 볼륨에 <code>Apache2</code>라는 디렉토리를 + 만든다</li> + + <li><code>APACHE2.NLM</code>과 <code>APRLIB.NLM</code>을 + <code>SYS:/APACHE2</code>에 복사한다</li> + + <li><code>SYS:/APACHE2</code> 아래에 <code>BIN</code>이라는 + 디렉토리를 만든다</li> + + <li><code>HTDIGEST.NLM</code>, <code>HTPASSWD.NLM</code>, + <code>HTDBM.NLM</code>, <code>LOGRES.NLM</code>, + <code>ROTLOGS.NLM</code>을 <code>SYS:/APACHE2/BIN</code>에 + 복사한다</li> + + <li><code>SYS:/APACHE2</code> 아래에 <code>CONF</code>라는 + 디렉토리를 만든다</li> + + <li><code>HTTPD-STD.CONF</code> 파일을 + <code>SYS:/APACHE2/CONF</code>에 복사하고 파일명을 + <code>HTTPD.CONF</code>로 변경한다</li> + + <li><code>MIME.TYPES</code>, <code>CHARSET.CONV</code>, + <code>MAGIC</code> 파일을 <code>SYS:/APACHE2/CONF</code> + 디렉토리에 복사한다</li> + + <li><code>\HTTPD-2.0\DOCS\ICONS</code>에 있는 모든 파일과 + 하위디렉토리를 <code>SYS:/APACHE2/ICONS</code>로 복사한다</li> + + <li><code>\HTTPD-2.0\DOCS\MANUAL</code>에 있는 모든 파일과 + 하위디렉토리를 <code>SYS:/APACHE2/MANUAL</code>로 복사한다</li> + + <li><code>\HTTPD-2.0\DOCS\ERROR</code>에 있는 모든 파일과 + 하위디렉토리를 <code>SYS:/APACHE2/ERROR</code>로 복사한다</li> + + <li><code>\HTTPD-2.0\DOCS\DICROOT</code>에 있는 모든 파일과 + 하위디렉토리를 <code>SYS:/APACHE2/HTDOCS</code>로 복사한다</li> + + <li>서버에 <code>SYS:/APACHE2/LOGS</code> 디렉토리를 만든다</li> + + <li>서버에 <code>SYS:/APACHE2/APACHE2/CGI-BIN</code>이란 + 디렉토리를 만든다</li> + + <li><code>SYS:/APACHE2/MODULES</code> 디렉토리를 만들고 + 모든 nlm 모듈을 <code>modules</code> 디렉토리로 복사한다</li> + + <li><code>HTTPD.CONF</code> 파일의 모든 <code>@@Value@@</code> + 표시를 적절한 설정으로 대체한다</li> + + <li><div class="example"><p><code>SEARCH ADD SYS:\APACHE2</code></p></div> 같이 검색경로에 + <code>SYS:/APACHE2</code>를 추가한다 + </li> + </ul> + + <p>기본 <code>SYS</code> 볼륨이 아닌 다른 볼륨에도 아파치를 + 설치할 수 있다.</p> + + <p>makefile 명령어에 "install" 키워드를 사용하면 컴파일시 + 자동으로 <code>DIST</code> 하위디렉토리에 완전한 배포본을 + 만든다. makefile로 만든 배포본을 NetWare 볼륨 최상위 디렉토리로 + 복사하면 아파치가 설치된다 (아래 <a href="#comp">NetWare용 + 아파치 컴파일하기</a> 참고).</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="run" id="run">NetWare용 아파치 실행하기</a></h2> + + + + <p>아파치를 시작하려면 콘솔에서 <code>apache</code>를 입력하면 + 된다. 그러면 운영체제 주소영역에 아파치를 읽어들인다. + 보호주소영역에 아파치를 읽어들이려면 다음과 같이 load 명령어로 + 주소영역을 지정한다:</p> + + <div class="example"><p><code> + load address space = apache2 apache2 + </code></p></div> + + <p>그러면 아파치를 apache2라는 주소영역에 읽어들인다. + NetWare는 여러 아파치를 각각 다른 보호주소영역에 읽어들여서 + 여러 아파치를 동시에 실행할 수 있다.</p> + + <p>아파치가 시작하면 (설정파일에서 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> 지시어를 수정하지 + 않는한) 포트 80번을 기다린다. 브라우저를 시작하여 서버명 + 혹은 서버 주소를 입력하면 서버에 접속하여 기본페이지에 + 접근한다. 아파치 설명서 링크가 있는 환영페이지가 나와야 + 한다. 아무 일도 없거나 오류가 발생하면 <code>logs</code> + 디렉토리에 있는 <code>error_log</code> 파일을 살펴봐라.</p> + + <p>기본 설치가 동작하면 <code>conf</code> 디렉토리에 있는 + 파일을 적절히 설정한다.</p> + + <p>운영체제 주소영역에서 실행중인 아파치를 내릴려면 콘솔에 + 다음과 같이 입력한다:</p> + + <div class="example"><p><code> + unload apache2 + </code></p></div> + + <p>혹은</p> + + <div class="example"><p><code> + apache2 shutdown + </code></p></div> + + <p>보호주소영역에서 아파치를 실행했다면 unload 명령어에 + 주소영역을 지정한다:</p> + + <div class="example"><p><code> + unload address space = apache2 apache2 + </code></p></div> + + <p>아파치가 설정파일 위치를 찾는 방법을 알아두어야 한다. + 명령행에서 설정파일을 지정하는 방법은 두가지다:</p> + + <ul> + <li><code>-f</code>는 특정 설정파일 경로를 지정한다</li> + </ul> + + <div class="example"><p><code> + apache2 -f "vol:/my server/conf/my.conf" + </code></p></div> + + <div class="example"><p><code> + apache -f test/test.conf + </code></p></div> + + <p>이 경우 설정파일은 올바른 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>를 설정해야 한다.</p> + + <p><code>-f</code>로 설정파일명을 지정하지 않으면, 아파치는 + 서버에 컴파일된 파일명을 (보통 <code>conf/httpd.conf</code>) + 사용한다. <code>-V</code> 옵션으로 아파치를 시작하면 + <code>SERVER_CONFIG_FILE</code>이라는 항목을 보여준다. + 아파치는 다음 순서대로 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>를 찾는다:</p> + + <ul> + <li><code>-C</code> 옵션의 <code>ServerRoot</code> 지시어.</li> + + <li>명령행의 <code>-d</code> 옵션.</li> + + <li>현재 디렉토리</li> + + <li>서버에 컴파일된 server root.</li> + </ul> + + <p>서버에 컴파일된 server root는 보통 + <code>sys:/apache2</code>이다. <code>-V</code> 옵션으로 + 아파치를 시작하면 <code>HTTPD_ROOT</code>라는 항목을 보여준다.</p> + + <p>NetWare용 아파치 2.0에는 실행중인 웹서버를 죽이거나 정보를 + 알려주는 명령행 지시어가 있다. 이들 지시어는 아파치 동작중에만 + 사용할 수 있다. 지시어 앞에는 <code>APACHE2</code> 키워드를 + 붙여야 한다.</p> + + <dl> + <dt>RESTART</dt> + <dd>모든 쓰레드가 쉬는 상태일때 아파치를 죽이고, 설정파일을 + 다시 읽은후 새로운 설정에 따라 worker 쓰레드들을 재시작한다.</dd> + + <dt>VERSION</dt> + <dd>현재 실행중인 아파치 버전 정보를 출력한다.</dd> + + <dt>MODULES</dt> + <dd>기본 모듈과 외부 모듈 목록을 출력한다.</dd> + + <dt>DIRECTIVES</dt> + <dd>모든 지시어 목록을 출력한다.</dd> + + <dt>SETTINGS</dt> + <dd>콘솔에 쓰레드 상태 표시를 보이거나 없앤다. 상태를 + 보이면, 아파치 콘솔창에 동작하는 쓰레드들의 상태가 나온다.</dd> + + <dt>SHUTDOWN</dt> + <dd>실행중인 아파치 웹서버를 죽인다.</dd> + + <dt>HELP</dt> + <dd>실행 옵션들을 설명한다.</dd> + </dl> + + <p>기본적으로 이 지시어들은 운영체제 주소영역에서 실행중인 + 아파치를 대상으로 한다. 아파치가 보호주소영역에서 실행중이라면, + -p와 주소영역 이름을 추가한다. 더 많은 정보를 보려면 명령행에 + "apache2 Help"를 입력한다.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="use" id="use">NetWare용 아파치 설정하기</a></h2> + + + + <p>아파치는 보통 <code>conf</code> 디렉토리에 있는 설정파일로 + 설정한다. 이 파일은 유닉스용과 같지만, NetWare용 아파치에는 + 조금 다른 지시어들이 있다. 사용가능한 모든 지시어에 대해서는 + <a href="../">아파치 문서</a>를 참고하라.</p> + + <p>NetWare용 아파치의 주된 차이점은:</p> + + <ul> + <li> + <p>NetWare용 아파치는 다중쓰레드 방식을 사용하기때문에, + 유닉스와 같이 요청마다 다른 프로세스를 사용하지 않는다. + 대신 여러 쓰레드를 실행한다: 부모 쓰레드와 요청을 처리하는 + 여러 자식 혹은 worker 쓰레드들.</p> + + <p>그러므로 "프로세스"-관리 지시어가 다르다:</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code> - + 유닉스와 같이 worker 쓰레드가 요청을 얼마만큼 처리하고 + 죽을지를 조정한다. 권장하는 기본값 + <code>MaxRequestsPerChild 0</code>을 사용하면 쓰레드는 + 죽지않고 영원히 요청을 서비스한다. 특별한 이유가 없다면 + NetWare에서는 이 지시어를 <code>0</code>으로 설정하길 + 권한다.</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#startthreads">StartThreads</a></code> - + 이 지시어는 서버가 처음에 시작할 쓰레드 개수를 결정한다. + 권장하는 기본값은 <code>StartThreads 50</code>이다.</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#minsparethreads">MinSpareThreads</a></code> - + 서버는 쉬는(idle) 쓰레드 개수가 이 값보다 적으면 worker + 쓰레드를 더 만든다. 권장하는 기본값은 + <code>MinSpareThreads 10</code>이다.</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#maxsparethreads">MaxSpareThreads</a></code> - + 서버는 쉬는 쓰레드 개수가 이 값보다 많으면 worker 쓰레드를 + 죽이기 시작한다. 권장하는 기본값은 + <code>MaxSpareThreads 100</code>이다.</p> + + <p><code class="directive"><a href="../mod/mpm_netware.html#maxthreads">MaxThreads</a></code> - + 이 지시어는 worker 쓰레드의 최대 개수를 제한한다. 권장하는 + 기본값은 <code>ThreadsPerChild 250</code>이다.</p> + + <p><code class="directive"><a href="../mod/mpm_netware.html#threadstacksize">ThreadStackSize</a></code> - + 한 worker 쓰레드가 사용할 스택 크기를 지시한다. 권장하는 + 기본값은 <code>ThreadStackSize 65536</code>이다.</p> + </li> + + <li> + <p>아규먼트로 파일명을 받는 지시어에는 유닉스 파일명이 + 아닌 NetWare 파일명을 사용해야 한다. 그러나 아파치가 + 내부적으로 유닉스식 파일명을 사용하기때문에 백슬래쉬 + 대신 슬래쉬를 사용해야 한다. 모든 절대경로에 볼륨명을 + 포함하길 바란다. 볼륨명을 생략하면 아파치는 + <code>SYS:</code> 볼륨이라고 잘못 가정할 수 있다.</p> + </li> + + <li> + <p>NetWare용 아파치는 서버를 다시 컴파일하지 않고 실행할때 + 모듈을 읽어들일 수 있다. 보통 아파치를 컴파일하면 + <code>\Apache2\modules</code> 디렉토리에 여러 추가 모듈을 + 설치한다. 이들 혹은 다른 모듈을 사용하려면 <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code> 지시어를 사용한다. + 예를 들어 status 모듈을 사용한다면:</p> + + <div class="example"><p><code> + LoadModule status_module modules/status.nlm + </code></p></div> + + <p><a href="../mod/mod_so.html#creating">읽어들일 수 + 있는 모듈 만들기</a>에 대한 정보도 있다.</p> + </li> + </ul> + + <h3><a name="use-add" id="use-add">이외의 NetWare 전용 지시어들:</a></h3> + + + + <ul> + <li><code class="directive"><a href="../mod/core.html#cgimapextension">CGIMapExtension</a></code> - + CGI 파일 확장자를 스크립트 인터프리터와 연결한다.</li> + </ul> + <ul> + <li><code class="directive"><a href="../mod/mod_nw_ssl.html#securelisten">SecureListen</a></code> - + 특정 포트를 SSL 암호화한다.</li> + </ul> + <ul> + <li><code class="directive"><a href="../mod/mod_nw_ssl.html#nwssltrustedcerts">NWSSLTrustedCerts</a></code> - + 프록시하는 서버에 보안연결할때 사용할 신뢰하는 + 인증서(certificate)를 추가한다.</li> + </ul> + <ul> + <li><code class="directive"><a href="../mod/mod_nw_ssl.html#nwsslupgradeable">NWSSLUpgradeable</a></code> - + 특정 주소/포트로 맺어진 연결을 SSL 연결로 변경할 수 + 있다.</li> + </ul> + + + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="comp" id="comp">Netware용 아파치 컴파일하기</a></h2> + + + + <p>아파치를 컴파일하려면 MetroWerks CodeWarrior 6.x 이상이 + 필요하다. 아파치를 컴파일하면 어떤 Netware 볼륨에라도 설치할 + 수 있다. 기본값은 <code>sys:/Apache2</code> 디렉토리다.</p> + + <p>서버를 실행하기 전에 <code>conf</code> 디렉토리를 작성해야 + 한다. 배포본의 <code>conf</code> 디렉토리에 있는 + <code>HTTPD-STD.CONF</code> 파일명을 <code>HTTPD.CONF</code>로 + 변경한다. <code>HTTPD.CONF</code> 파일에서 <code>@@Value@@</code> + 표시를 찾아서 적절한 설정으로 대체한다. <code>conf/magic</code>과 + <code>conf/mime.types</code> 파일도 복사한다. 아니면 makefile을 + 실행할때 <code>install</code> 키워드를 사용하면 완전한 배포본을 + 만든다.</p> + + <h3><a name="comp-req" id="comp-req">요구사항:</a></h3> + + + + <p>NetWare용 아파치 2.0을 컴파일하려면 다음 개발도구가 + 필요하다:</p> + + <ul> + <li>Metrowerks CodeWarrior 6.0 이상과 <a href="http://developer.novell.com/ndk/cwpdk.htm">NetWare + PDK 3.0</a> 이상.</li> + + <li><a href="http://developer.novell.com/ndk/libc.htm">NetWare + Libraries for C (LibC)</a></li> + + <li><a href="http://developer.novell.com/ndk/cldap.htm">LDAP + Libraries for C</a></li> + + <li><a href="http://www.gzip.org/zlib/">ZLIB 압축 라이브러리 + 소스코드</a></li> + + <li>AWK 도구 (awk, gawk 등). AWK는 <a href="http://developer.novell.com/ndk/apache.htm">http://developer.novell.com/ndk/apache.htm</a>에서 + 다운받을 수 있다. 도구를 <code>awk.exe</code>란 이름으로 + 윈도우즈 경로에 두어야 한다.</li> + + <li>makefile을 사용하여 컴파일하려면 <a href="http://developer.novell.com/ndk/apache.htm">http://developer.novell.com/ndk/apache.htm</a>에 + 있는 GNU make 버전 3.78.1 (GMake)이 필요하다.</li> + </ul> + + + + <h3><a name="comp-make" id="comp-make">NetWare makefile을 사용하여 아파치 컴파일하기:</a></h3> + + + + <ul> + <li><code>NOVELLLIBC</code> 환경변수를 + <div class="example"><p><code>Set NOVELLLIBC=c:\novell\ndk\libc</code></p></div>와 + 같이 NetWare Libraries for C SDK 위치로 설정한다. + </li> + + <li><code>METROWERKS</code> 환경변수를 + <div class="example"><p><code>Set METROWERKS=C:\Program Files\Metrowerks\CodeWarrior</code></p></div>와 + 같이 Metrowerks CodeWarrior 컴파일러를 설치한 위치로 + 설정한다. 기본 위치인 + <code>C:\Program Files\Metrowerks\CodeWarrior</code>에 + 설치하였다면, 환경변수를 설정할 필요는 없다.</li> + + <li><code>LDAPSDK</code> 환경변수를 + <div class="example"><p><code>Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc</code></p></div>와 + 같이 LDAP Libraries for C를 설치한 위치로 설정한다. + </li> + + <li><code>ZLIBSDK</code> 환경변수를 + <div class="example"><p><code>Set ZLIBSDK=D:\NOVELL\zlib</code></p></div>과 같이 + ZLib 라이브러리 소스코드 위치로 설정한다. + </li> + + <li><code>AP_WORK</code> 환경변수를 <code>\httpd-2.0</code> + 디렉토리의 전체 경로로 설정한다.</li> + + <li><code>APR_WORK</code> 환경변수를 + <code>\httpd-2.0\srclib\apr</code> 디렉토리의 전체 경로로 + 설정한다.</li> + + <li>AWK 도구와 GNU make (<code>gmake.exe</code>) 도구가 + 시스템의 <code>PATH</code> 환경변수에 포함되있는지 + 확인한다.</li> + + <li>소스코드를 다운받아 적당한 디렉토리에 압축을 푼다.</li> + + <li><code>\httpd-2.0\srclib\apr-util\uri</code> 디렉토리에서 + "<code>gmake -f nwgnumakefile</code>"을 실행하여 + <code>GENURI.nlm</code>을 컴파일한다.</li> + + <li><code>GENURI.nlm</code> 파일을 NetWare 서버의 + <code>SYS:</code> 볼륨으로 복사하고 + <div class="example"><p><code>SYS:\genuri > sys:\uri_delims.h</code></p></div> + 명령을 실행한다. + </li> + + <li><code>uri_delims.h</code> 파일을 컴파일하는 컴퓨터의 + <code>\httpd-2.0\srclib\apr-util\uri</code> 디렉토리로 + 복사한다.</li> + + <li><code>\httpd-2.0\srclib\apr</code> 디렉토리에서 + "<code>gmake -f nwgnumakefile</code>"을 실행하여 APR을 + 컴파일한다.</li> + + <li><code>\httpd-2.0\srclib\pcre</code> 디렉토리에서 + "<code>gmake -f nwgnumakefile</code>"을 실행하여 + <code>DFTABLES.nlm</code>을 컴파일한다.</li> + + <li><code>\httpd-2.0\server</code> 디렉토리에서 + "<code>gmake -f nwgnumakefile</code>"을 실행하여 + <code>GENCHARS.nlm</code>을 컴파일한다.</li> + + <li>각 디렉토리의 <code>GENCHARS.nlm</code>과 + <code>DFTABLES.nlm</code> 파일을 NetWare 서버의 + <code>SYS:</code> 볼륨으로 복사하고 다음과 같이 실행한다: + <div class="example"><p><code> + SYS:\genchars > sys:\test_char.h<br /> + SYS:\dftables > sys:\chartables.c<br /> + </code></p></div> + </li> + + <li><code>test_char.h</code>와 <code>chartables.c</code> + 파일을 컴파일하는 컴퓨터의 <code>\httpd-2.0\os\netware</code> + 디렉토리로 복사한다.</li> + + <li><code>\httpd-2.0</code> 디렉토리에서 + "<code>gmake -f nwgnumakefile</code>"을 실행하여 아파치를 + 컴파일한다. + <div class="example"><p><code>gmake -f nwgnumakefile install</code></p></div>과 + 같이 install 파라미터를 추가하면 배포용 디렉토리를 만들 + 수 있다. + </li> + </ul> + + + + <h3><a name="comp-add" id="comp-add">추가 make 옵션</a></h3> + + + + <ul> + <li><code>gmake -f nwgnumakefile</code><p>일반 실행파일을 + 컴파일하여 <code>\release</code> 디렉토리로 복사한다.</p></li> + + <li><code>gmake -f nwgnumakefile DEBUG=1</code><p>디버그용 + 실행파일을 컴파일하여 <code>\debug</code> 디렉토리로 + 복사한다.</p></li> + + <li><code>gmake -f nwgnumakefile install</code> + <p><code>\dist\Apache2</code> 디렉토리에 실행파일, 문서, + 추가 지원파일을 포함한 완전한 아파치 배포본을 만든다.</p></li> + + <li><code>gmake -f nwgnumakefile installdev</code> + <p>install과 비슷하지만, <code>\lib</code>과 + <code>\include</code> 디렉토리를 만들고 헤더파일과 import + 파일을 복사한다.</p></li> + + <li><code>gmake -f nwgnumakefile clean</code> + <p><code>DEBUG</code> 정의 유무에 따라 <code>\release</code>나 + <code>\debug</code>에 있는 오브젝트파일과 실행파일을 + 모두 지운다.</p></li> + + <li><code>gmake -f nwgnumakefile clobber_all</code><p>clean과 + 비슷하지만 디렉토리도 지운다.</p></li> + </ul> + + + + </div></div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/platform/netware.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/netware.html" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/perf-hp.html b/rubbos/app/httpd-2.0.64/docs/manual/platform/perf-hp.html new file mode 100644 index 00000000..951a04bd --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/perf-hp.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: perf-hp.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: perf-hp.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/perf-hp.html.en b/rubbos/app/httpd-2.0.64/docs/manual/platform/perf-hp.html.en new file mode 100644 index 00000000..8ff50e52 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/perf-hp.html.en @@ -0,0 +1,105 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Running a High-Performance Web Server on HPUX - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page" class="no-sidebar"><div id="page-header"> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Running a High-Performance Web Server on HPUX</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/platform/perf-hp.html" title="English"> en </a> | +<a href="../ko/platform/perf-hp.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div> + + +<pre> +Date: Wed, 05 Nov 1997 16:59:34 -0800 +From: Rick Jones <<a href="mailto:raj@cup.hp.com">raj@cup.hp.com</a>> +Reply-To: <a href="mailto:raj@cup.hp.com">raj@cup.hp.com</a> +Organization: Network Performance +Subject: HP-UX tuning tips +</pre> + + <p>Here are some tuning tips for HP-UX to add to the tuning page.</p> + + <p>For HP-UX 9.X: Upgrade to 10.20<br /> + For HP-UX 10.[00|01|10]: Upgrade to 10.20</p> + + <p>For HP-UX 10.20:</p> + + <p>Install the latest cumulative ARPA Transport Patch. This + will allow you to configure the size of the TCP connection + lookup hash table. The default is 256 buckets and must be set + to a power of two. This is accomplished with adb against the + *disc* image of the kernel. The variable name is <code>tcp_hash_size</code>. + Notice that it's critically important that you use "<code>W</code>" + to write a 32 bit quantity, not "<code>w</code>" to write a 16 bit + value when patching the disc image because the <code>tcp_hash_size</code> + variable is a 32 bit quantity.</p> + + <p>How to pick the value? Examine the output of <a href="ftp://ftp.cup.hp.com/dist/networking/tools/connhist">ftp://ftp.cup.hp.com/dist/networking/tools/connhist</a> + and see how many total TCP connections exist on the system. You + probably want that number divided by the hash table size to be + reasonably small, say less than 10. Folks can look at HP's + SPECweb96 disclosures for some common settings. These can be + found at <a href="http://www.specbench.org/">http://www.specbench.org/</a>. + If an HP-UX system was performing at 1000 SPECweb96 connections + per second, the <code>TIME_WAIT</code> time of 60 seconds would mean + 60,000 TCP "connections" being tracked.</p> + + <p>Folks can check their listen queue depths with <a href="ftp://ftp.cup.hp.com/dist/networking/misc/listenq">ftp://ftp.cup.hp.com/dist/networking/misc/listenq</a>.</p> + + <p>If folks are running Apache on a PA-8000 based system, they + should consider "chatr'ing" the Apache executable to have a + large page size. This would be "<code>chatr +pi L <BINARY></code>". + The GID of the running executable must have <code>MLOCK</code> privileges. + <code>Setprivgrp(1m)</code> should be consulted for assigning + <code>MLOCK</code>. The change can be validated by running Glance + and examining the memory regions of the server(s) to make sure that + they show a non-trivial fraction of the text segment being locked.</p> + + <p>If folks are running Apache on MP systems, they might + consider writing a small program that uses <code>mpctl()</code> + to bind processes to processors. A simple <code>pid % numcpu</code> + algorithm is probably sufficient. This might even go into the + source code.</p> + + <p>If folks are concerned about the number of <code>FIN_WAIT_2</code> + connections, they can use nettune to shrink the value of + <code>tcp_keepstart</code>. However, they should be careful there - + certainly do not make it less than oh two to four minutes. If + <code>tcp_hash_size</code> has been set well, it is probably OK to + let the <code>FIN_WAIT_2</code>'s take longer to timeout (perhaps + even the default two hours) - they will not on average have a big + impact on performance.</p> + + <p>There are other things that could go into the code base, but + that might be left for another email. Feel free to drop me a + message if you or others are interested.</p> + + <p>sincerely,</p> + + <p>rick jones</p> + + <p><a href="http://www.cup.hp.com/netperf/NetperfPage.html">http://www.cup.hp.com/netperf/NetperfPage.html</a></p> + + </div> +</div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/platform/perf-hp.html" title="English"> en </a> | +<a href="../ko/platform/perf-hp.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/perf-hp.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/platform/perf-hp.html.ko.euc-kr new file mode 100644 index 00000000..fa1568e2 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/perf-hp.html.ko.euc-kr @@ -0,0 +1,100 @@ +<?xml version="1.0" encoding="EUC-KR"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ko" xml:lang="ko"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>HPUX에서 고성능 웹서버 실행하기 - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page" class="no-sidebar"><div id="page-header"> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>HPUX에서 고성능 웹서버 실행하기</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/platform/perf-hp.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/perf-hp.html" title="Korean"> ko </a></p> +</div> + + +<pre> +Date: Wed, 05 Nov 1997 16:59:34 -0800 +From: Rick Jones <<a href="mailto:raj@cup.hp.com">raj@cup.hp.com</a>> +Reply-To: <a href="mailto:raj@cup.hp.com">raj@cup.hp.com</a> +Organization: Network Performance +Subject: HP-UX tuning tips +</pre> + + <p>이 글은 성능향상 페이지에 추가할 HP-UX 성능향상 팁이다.</p> + + <p>HP-UX 9.X는: 10.20으로 업그레이드하라<br /> + HP-UX 10.[00|01|10]은: 10.20으로 업그레이드하라</p> + + <p>HP-UX 10.20은:</p> + + <p>최근 ARPA Transport 패치 모음을 설치한다. 그러면 TCP + 연결찾기 해쉬테이블 크기를 설정할 수 있다. 기본값은 + 256 개이고, 2의 거듭제곱값으로 지정해야 한다. adb로 커널의 + *disc* 이미지를 수정하여 설정한다. 변수명은 + <code>tcp_hash_size</code>이다. <code>tcp_hash_size</code> + 변수값이 32비트이므로 disc 이미지를 수정할때 반드시 16비트 + 값을 기록하는 "<code>w</code>" 대신 32비트 값을 기록하는 + "<code>W</code>"를 사용해야 한다.</p> + + <p>어떤 값을 고를까? <a href="ftp://ftp.cup.hp.com/dist/networking/tools/connhist">ftp://ftp.cup.hp.com/dist/networking/tools/connhist</a>의 + 결과를 보고, 시스템에 존재하는 TCP 연결 총개수를 살펴봐라. + 이 숫자를 해쉬테이블 크기로 나눈 값이 상당히 (10 이하) 작으면 + 좋다. HP의 SPECweb96 결과에서 일반적인 설정을 볼 수 있다. + 결과는 <a href="http://www.specbench.org/">http://www.specbench.org/</a>에 + 있다. HP-UX 시스템이 초당 1000번 SPECweb96 연결을 하는 경우 + <code>TIME_WAIT</code>가 60초라면 60,000개의 TCP "연결"을 + 추적한다는 뜻이다.</p> + + <p><a href="ftp://ftp.cup.hp.com/dist/networking/misc/listenq">ftp://ftp.cup.hp.com/dist/networking/misc/listenq</a>를 + 실행하여 시스템의 연결대기행렬 깊이를 알 수 있다.</p> + + <p>PA-8000기반 시스템에서 아파치를 실행한다면, 아파치 + 실행파일이 큰 페이지크기를 사용하도록 "chatr"한다. 명령은 + "<code>chatr +pi L <실행파일></code>"이다. 실행파일을 + 실행하는 GID에 <code>MLOCK</code> 권한이 반드시 필요하다. + <code>MLOCK</code> 부여에 대해서는 <code>Setprivgrp(1m)</code>를 + 참고하라. 수정후 Glance를 실행하여 서버의 메모리영역을 살펴보면 + 상당한 text 세그먼트가 잠겨있음을 확인할 수 있다.</p> + + <p>다중프로세스 시스템에서 아파치를 실행한다면, 프로세스를 + 프로세스에 배정하는 <code>mpctl()</code>를 사용한 작은 + 프로그램을 작성해봐라. 단순한 <code>pid % numcpu</code> + 알고리즘으로도 충분할 것이다. 이 부분은 앞으로 소스코드에 + 포함될 수 있다.</p> + + <p><code>FIN_WAIT_2</code> 연결의 개수가 걱정스럽다면, + nettune을 사용하여 <code>tcp_keepstart</code> 값을 줄일 + 수 있다. 그러나 조심해야 한다 - 4분 보다 작게 설정하지 마라. + <code>tcp_hash_size</code>를 잘 설정하였다면, + <code>FIN_WAIT_2</code> 값이 커도 (심지어 기본값인 2시간도) + 문제없다 - 보통 성능에 큰 영향을 주지 않는다.</p> + + <p>앞으로 소스코드에 포함될 부분이 더 있지만, 여기서 줄인다. + 관심이 있다면 메일을 주길 바란다.</p> + + <p>그럼 이만,</p> + + <p>rick jones</p> + + <p><a href="http://www.cup.hp.com/netperf/NetperfPage.html">http://www.cup.hp.com/netperf/NetperfPage.html</a></p> + + </div> +</div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/platform/perf-hp.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/perf-hp.html" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/win_compiling.html b/rubbos/app/httpd-2.0.64/docs/manual/platform/win_compiling.html new file mode 100644 index 00000000..2ac828ca --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/win_compiling.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: win_compiling.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: win_compiling.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/win_compiling.html.en b/rubbos/app/httpd-2.0.64/docs/manual/platform/win_compiling.html.en new file mode 100644 index 00000000..96a130a7 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/win_compiling.html.en @@ -0,0 +1,431 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Compiling Apache for Microsoft Windows - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Compiling Apache for Microsoft Windows</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/platform/win_compiling.html" title="English"> en </a> | +<a href="../ko/platform/win_compiling.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div> + + + <p>There are many important points before you begin compiling + Apache. See <a href="windows.html">Using Apache with Microsoft + Windows</a> before you begin.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#requirements">Requirements</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#commandbuild">Command-Line Build</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#workspacebuild">Developer Studio Workspace IDE Build</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#projectcomponents">Project Components</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="requirements" id="requirements">Requirements</a></h2> + + + + <p>Compiling Apache requires the following environment to be + properly installed:</p> + + <ul> + <li> + <p>Disk Space</p> + <p>Make sure you have at least 50 MB of free disk space + available. After installation Apache requires approximately + 10 MB of disk space, plus space for log and cache files, + which can grow rapidly. The actual disk space requirements + will vary considerably based on your chosen configuration and + any third-party modules or libraries.</p> + </li> + + <li> + <p>Microsoft Visual C++ 5.0 or higher.</p> + <p>Apache can be built using the command line tools, or from + within the Visual Studio IDE Workbench. The command line + build requires the environment to reflect the <code>PATH</code>, + <code>INCLUDE</code>, <code>LIB</code> and other variables + that can be configured with the <code>vcvars32</code> batch file:</p> + + <div class="example"><p><code> + "c:\Program Files\DevStudio\VC\Bin\vcvars32.bat" + </code></p></div> + </li> + + <li> + <p>The Windows Platform SDK.</p> + <p>Visual C++ 5.0 builds require an updated Microsoft Windows + Platform SDK to enable some Apache features. For command line + builds, the Platform SDK environment is prepared by the + <code>setenv</code> batch file:</p> + + <div class="example"><p><code> + "c:\Program Files\Platform SDK\setenv.bat" + </code></p></div> + + <p>The Platform SDK files distributed with Visual C++ 6.0 and + later are sufficient, so users of later version may skip + this requirement.</p> + + <div class="note">Note that the Windows Platform SDK update is required + to enable all supported <code class="module"><a href="../mod/mod_isapi.html">mod_isapi</a></code> features. + Without a recent update, Apache will issue warnings under + MSVC++ 5.0 that some <code class="module"><a href="../mod/mod_isapi.html">mod_isapi</a></code> features + will be disabled. Look for the update at <a href="http://msdn.microsoft.com/downloads/sdks/platform/platform.asp">http://msdn.microsoft.com/downloads/sdks/platform/platform.asp</a>.</div> + </li> + + <li> + <p>The awk utility (awk, gawk or similar).</p> + <p>To install Apache within the build system, several files are + modified using the <code>awk.exe</code> utility. awk was chosen since it + is a very small download (compared with Perl or WSH/VB) and + accomplishes the task of generating files. Brian Kernighan's + <a href="http://cm.bell-labs.com/cm/cs/who/bwk/">http://cm.bell-labs.com/cm/cs/who/bwk/</a> + site has a compiled native Win32 binary, + <a href="http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe">http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe</a> which + you must save with the name <code>awk.exe</code> rather than + <code>awk95.exe</code>.</p> + + <div class="note">Note that Developer Studio IDE will only find + <code>awk.exe</code> from the Tools menu Options... Directories + tab (the Projects - VC++ Directories pane in Developer Studio 7.0) + listing Executable file paths. Add the path for <code>awk.exe</code> + to this list, and your system <code>PATH</code> environment variable, + as needed.</div> + + <div class="note">Also note that if you are using Cygwin (<a href="http://www.cygwin.com/">http://www.cygwin.com/</a>) the awk utility is named <code>gawk.exe</code> and + that the file <code>awk.exe</code> is really a symlink to the <code>gawk.exe</code> + file. The Windows command shell does not recognize symlinks, and because of that + building InstallBin will fail. A workaround is to delete <code>awk.exe</code> from + the cygwin installation and rename <code>gawk.exe</code> to <code>awk.exe</code>.</div> + </li> + + <li> + <p>[Optional] OpenSSL libraries (for <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> + and <code>ab.exe</code> with ssl support)</p> + <p><strong>Caution: there are significant restrictions and + prohibitions on the use and distribution of strong cryptography + and patented intellectual property throughout the world.</strong> + OpenSSL includes strong cryptography controlled by both export + regulations and domestic law, as well as intellectual property + protected by patent, in the United States and elsewhere. Neither + the Apache Software Foundation nor the OpenSSL project can provide + legal advise regarding possession, use, or distribution of the code + provided by the OpenSSL project. <strong>Consult your own legal + counsel, you are responsible for your own actions.</strong></p> + + <p>OpenSSL must be installed into a <code>srclib</code> subdirectory named + <code>openssl</code>, obtained from <a href="http://www.openssl.org/source/">http://www.openssl.org/source/</a>, in order to compile <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> + or the abs project (<code>ab.exe</code> with SSL support.) To prepare OpenSSL + for both <code>release</code> and <code>debug</code> builds of Apache, and + disable the patent protected features in OpenSSL, you might use the following + build commands:</p> + + <div class="example"><p><code> + perl Configure VC-WIN32<br /> + perl util\mkfiles.pl >MINFO<br /> + perl util\mk1mf.pl dll no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile.rel<br /> + perl util\mk1mf.pl dll debug no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile.dbg<br /> + perl util\mkdef.pl 32 libeay no-asm no-mdc2 no-rc5 no-idea >ms\libeay32.def<br /> + perl util\mkdef.pl 32 ssleay no-asm no-mdc2 no-rc5 no-idea >ms\ssleay32.def<br /> + nmake -f makefile.rel<br /> + nmake -f makefile.dbg + </code></p></div> + + <p>Note; you can use the scripts in the <code>ms\</code> subdirectory, however, + it's rather tricky to force <code>ms\do_masm.bat</code>, for example, to perform + the patent encumberances as mentioned above. Patches to add the $* argument list + to the appropriate .bat lines in these scripts aren't incorporated, thus far.</p> + </li> + + <li> + <p>[Optional] zlib sources (for <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>)</p> + <p>Zlib must be installed into a <code>srclib</code> subdirectory named + <code>zlib</code>, however those sources need not be compiled. The build system + will compile the compression sources directly into the <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code> + module. Zlib can be obtained from <a href="http://www.zlib.net/">http://www.zlib.net/</a> -- <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code> is confirmed to build + correctly with version 1.1.4. To use a later version of zlib, upgrade to + Apache HTTP Server release 2.2 or later.</p> + </li> + + </ul> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="commandbuild" id="commandbuild">Command-Line Build</a></h2> + + + + <p>First, unpack the Apache distribution into an appropriate + directory. Open a command-line prompt and <code>cd</code> to that + directory.</p> + + <p>The master Apache makefile instructions are contained in the + <code>Makefile.win</code> file. To compile Apache on Windows + NT, simply use one of the following commands to compiled the + <code>release</code> or <code>debug</code> build, respectively:</p> + + <div class="example"><pre> +nmake /f Makefile.win _apacher + +nmake /f Makefile.win _apached + </pre></div> + + <p>Either command will compile Apache. The latter will include + debugging information in the resulting files, making it easier + to find bugs and track down problems.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="workspacebuild" id="workspacebuild">Developer Studio Workspace IDE Build</a></h2> + + + + <p>Apache can also be compiled using VC++'s Visual Studio + development environment. To simplify this process, a + Visual Studio workspace, <code>Apache.dsw</code>, is provided. + This workspace exposes the entire list of working <code>.dsp</code> + projects that are required for the complete Apache binary release. + It includes dependencies between the projects to assure that they + are built in the appropriate order.</p> + + <p>Open the <code>Apache.dsw</code> workspace, and select + <code>InstallBin</code> (<code>Release</code> or <code>Debug</code> build, + as desired) as the Active Project. <code>InstallBin</code> causes all + related project to be built, and then invokes <code>Makefile.win</code> to + move the compiled executables and dlls. You may personalize the + <code>INSTDIR=</code> choice by changing <code>InstallBin</code>'s Settings, + General tab, Build command line entry. <code>INSTDIR</code> defaults to the + <code>/Apache2</code> directory. If you only want a test compile (without + installing) you may build the <code>BuildBin</code> project instead.</p> + + <p>The <code>.dsp</code> project files are distributed in Visual + C++ 6.0 format. Visual C++ 5.0 (97) will recognize them. Visual C++ + 7.0 (.net) must convert <code>Apache.dsw</code> plus the <code>.dsp</code> + files into an <code>Apache.sln</code> plus <code>.msproj</code> files, + be sure you reconvert the <code>.msproj</code> file if any of the source + <code>.dsp</code> files change! This is really trivial, just open + <code>Apache.dsw</code> in the VC++ 7.0 IDE once again.</p> + + <p>Visual C++ 7.0 (.net) users should also use the Build + menu, Configuration Manager dialog to uncheck both the <code>Debug</code> + and <code>Release</code> Solution modules abs, <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> + and <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>. + These modules are built by invoking <code>nmake</code> or the IDE directly + with the <code>BinBuild</code> target to build those modules explicitly, + only if the <code>srclib</code> directories <code>openssl</code> + and/or <code>zlib</code> exist.</p> + + <p>Exported <code>.mak</code> files pose a greater hassle, but they are + required for Visual C++ 5.0 users to build <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>, + abs (<code class="program"><a href="../programs/ab.html">ab</a></code> with SSL support) and/or + <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>. + VC++ 7.0 (.net) users also benefit, <code>nmake</code> builds + are faster than <code>binenv</code> builds. + Build the entire project from within the VC++ 5.0 or 6.0 IDE, + then use the Project Menu Export for all makefiles. + You must build the projects first in order to create all dynamic + auto-generated targets, so that dependencies can be parsed + correctly. Run the following command to fix the paths so they + will build anywhere:</p> + + <div class="example"><p><code> + perl srclib\apr\build\fixwin32mak.pl + </code></p></div> + + <p>You must type this command from the <em>top level</em> + directory of the httpd source tree. Every + <code>.mak</code> and <code>.dep</code> project file within + the current directory and below will be corrected, and the + timestamps adjusted to reflect the <code>.dsp</code>.</p> + + <p>If you contribute back a patch that revises project files, we + must commit project files in Visual Studio 6.0 format. Changes + should be simple, with minimal compilation and linkage flags that + will be recognized by all VC++ 5.0 through 7.0 environments.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="projectcomponents" id="projectcomponents">Project Components</a></h2> + + + + <p>The <code>Apache.dsw</code> workspace and <code>makefile.win</code> + <code>nmake</code> script both build the <code>.dsp</code> projects + of the Apache server in the following sequence:</p> + + <ol> + <li><code>srclib\apr\apr.dsp</code></li> + + <li><code>srclib\apr\libapr.dsp</code></li> + + <li><code>srclib\apr-util\uri\gen_uri_delims.dsp</code></li> + + <li><code>srclib\apr-util\xml\expat\lib\xml.dsp</code></li> + + <li><code>srclib\apr-util\aprutil.dsp</code></li> + + <li><code>srclib\apr-util\libaprutil.dsp</code></li> + + <li><code>srclib\pcre\dftables.dsp</code></li> + + <li><code>srclib\pcre\pcre.dsp</code></li> + + <li><code>srclib\pcre\pcreposix.dsp</code></li> + + <li><code>server\gen_test_char.dsp</code></li> + + <li><code>libhttpd.dsp</code></li> + + <li><code>Apache.dsp</code></li> + </ol> + + <p>In addition, the <code>modules\</code> subdirectory tree contains + project files for the majority of the modules.</p> + + <p>The <code>support\</code> directory contains project files for + additional programs that are not part of the Apache runtime, + but are used by the administrator to test Apache and maintain + password and log files. Windows-specific support projects are + broken out in the <code>support\win32\</code> directory.</p> + + <ol> + <li><code>support\ab.dsp</code></li> + + <li><code>support\htdigest.dsp</code></li> + + <li><code>support\htpasswd.dsp</code></li> + + <li><code>support\logresolve.dsp</code></li> + + <li><code>support\rotatelogs.dsp</code></li> + + <li><code>support\win32\ApacheMonitor.dsp</code></li> + + <li><code>support\win32\wintty.dsp</code></li> + </ol> + + <p>Once Apache has been compiled, it needs to be installed in + its server root directory. The default is the + <code>\Apache2</code> directory, of the same drive.</p> + + <p>To build and install all the files into the desired folder + <em>dir</em> automatically, use one of the following + <code>nmake</code> commands:</p> + + <div class="example"><pre> +nmake /f Makefile.win installr INSTDIR=<em>dir</em> + +nmake /f Makefile.win installd INSTDIR=<em>dir</em> + </pre></div> + + <p>The <em>dir</em> argument to <code>INSTDIR</code> gives + the installation directory; it can be omitted if Apache is + to be installed into <code>\Apache2</code>.</p> + + <p>This will install the following:</p> + + <ul> + <li><code><em>dir</em>\bin\Apache.exe</code> - Apache + executable</li> + + <li><code><em>dir</em>\bin\ApacheMonitor.exe</code> - Service + monitor taskbar icon utility</li> + + <li><code><em>dir</em>\bin\htdigest.exe</code> - Digest auth + password file utility</li> + + <li><code><em>dir</em>\bin\htdbm.exe</code> - SDBM auth + database password file utility</li> + + <li><code><em>dir</em>\bin\htpasswd.exe</code> - Basic auth + password file utility</li> + + <li><code><em>dir</em>\bin\logresolve.exe</code> - Log file + dns name lookup utility</li> + + <li><code><em>dir</em>\bin\rotatelogs.exe</code> - Log file + cycling utility</li> + + <li><code><em>dir</em>\bin\wintty.exe</code> - Console window + utility</li> + + <li><code><em>dir</em>\bin\libapr.dll</code> - Apache + Portable Runtime shared library</li> + + <li><code><em>dir</em>\bin\libaprutil.dll</code> - Apache + Utility Runtime shared library</li> + + <li><code><em>dir</em>\bin\libhttpd.dll</code> - Apache Core + library</li> + + <li><code><em>dir</em>\modules\mod_*.so</code> - Loadable + Apache modules</li> + + <li><code><em>dir</em>\conf</code> - Configuration + directory</li> + + <li><code><em>dir</em>\logs</code> - Empty logging + directory</li> + + <li><code><em>dir</em>\include</code> - C language header + files</li> + + <li><code><em>dir</em>\lib</code> - Link library files</li> + </ul> + + <h3><a name="projectcomponents-warn" id="projectcomponents-warn">Warning about building Apache from the development tree</a></h3> + + + + <div class="note">Note only the <code>.dsp</code> files are maintained between <code>release</code> + builds. The <code>.mak</code> files are NOT regenerated, due to the tremendous + waste of reviewer's time. Therefore, you cannot rely on the <code>NMAKE</code> + commands above to build revised <code>.dsp</code> project files unless you + then export all <code>.mak</code> files yourself from the project. This is + unnecessary if you build from within the Microsoft + Developer Studio environment.</div> + + <div class="note">Also note it is very worthwhile to build the <code>BuildBin</code> + target project (or the command line <code>_apacher</code> or + <code>_apached</code> target) prior to exporting the make files. + Many files are autogenerated in the build process. Only a full + build provides all of the dependent files required to build proper + dependency trees for correct build behavior.</div> + + <p>In order to create distribution <code>.mak</code> files, always review + the generated <code>.mak</code> (or <code>.dep</code>) dependencies for + Platform SDK or other garbage includes. The <code>DevStudio\SharedIDE\bin\</code> + (VC5) or <code>DevStudio\Common\MSDev98\bin\</code> (VC6) directory contains + the <code>sysincl.dat</code> file, which must list all exceptions. Update this + file (including both forward and backslashed paths, such as both + <code>sys/time.h</code> and <code>sys\time.h</code>) to include such dependencies. + Including local-install paths in a distributed <code>.mak</code> file will + cause the build to fail completely. And don't forget to run + <code>srclib/apr/build/fixwin32mak.pl</code> in order to fix absolute + paths within the <code>.mak</code> files.</p> + + + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/platform/win_compiling.html" title="English"> en </a> | +<a href="../ko/platform/win_compiling.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/win_compiling.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/platform/win_compiling.html.ko.euc-kr new file mode 100644 index 00000000..fccb14b6 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/win_compiling.html.ko.euc-kr @@ -0,0 +1,423 @@ +<?xml version="1.0" encoding="EUC-KR"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ko" xml:lang="ko"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Microsoft Windows용 아파치 컴파일 - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Microsoft Windows용 아파치 컴파일</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/platform/win_compiling.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/win_compiling.html" title="Korean"> ko </a></p> +</div> +<div class="outofdate">이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.</div> + + + <p>아파치를 컴파일하기 전에 주의할 점이 많다. 미리 <a href="windows.html">Microsoft Windows에서 아파치 사용법</a>을 + 참고하라.</p> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#requirements">요구사항</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#commandbuild">명령행에서 컴파일하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#workspacebuild">Developer Studio Workspace IDE에서 컴파일하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#projectcomponents">프로젝트 구성요소</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="requirements" id="requirements">요구사항</a></h2> + + + + <p>아파치를 컴파일하려면 다음이 정상적으로 설치되야 한다:</p> + + <ul> + <li> + <p>디스크 공간</p> + <p>남은 디스크 공간이 최소한 50 MB는 되야 한다. 아파치 + 설치후에는 빨리 증가하는 로그와 캐쉬파일을 제외하고 + 약 10 MB 정도가 필요하다. 실제 디스크 사용량은 선택한 + 구성과 제삼자가 만든 모듈 혹은 라이브러리에 따라 크게 + 다르다.</p> + </li> + + <li> + <p>Microsoft Visual C++ 5.0 이상.</p> + <p>아파치는 명령행 도구를 사용하거나 Visual Studio IDE + Workbench 안에서 컴파일할 수 있다. 명령행에서 컴파일한다면 + <code>vcvars32</code> 배치파일이 설정하는 <code>PATH</code>, + <code>INCLUDE</code>, <code>LIB</code> 등 환경변수가 + 필요하다:</p> + + <div class="example"><p><code> + "c:\Program Files\DevStudio\VC\Bin\vcvars32.bat" + </code></p></div> + </li> + + <li> + <p>Windows Platform SDK.</p> + <p>어떤 아파치 기능을 사용하려면 Visual C++ 5.0에 추가로 + 최신 Microsoft Windows Platform SDK가 필요하다. 명령행에서 + 컴파일한다면 <code>setenv</code> 배치파일이 Platform + SDK 환경을 만든다:</p> + + <div class="example"><p><code> + "c:\Program Files\Platform SDK\setenv.bat" + </code></p></div> + + <p>Visual C++ 6.0 이상에 포함된 Platform SDK 파일은 + 충분하다. 이 버전을 사용하는 사용자는 이 과정을 생략해도 + 된다.</p> + + <div class="note">모든 <code class="module"><a href="../mod/mod_isapi.html">mod_isapi</a></code> 기능을 사용하려면 + 최신 Windows Platform SDK가 필요하다. 최신 버전이 아니면 + MSVC++ 5.0은 <code class="module"><a href="../mod/mod_isapi.html">mod_isapi</a></code> 기능의 일부를 + 사용할 수 없다고 경고한다. <a href="http://msdn.microsoft.com/downloads/sdks/platform/platform.asp">http://msdn.microsoft.com/downloads/sdks/platform/platform.asp</a>에 + 최신 버전이 있다.</div> + </li> + + <li> + <p>awk 도구 (awk, gawk 등).</p> + <p>컴파일한 시스템에 아파치를 설치하려면 + <code>awk.exe</code> 도구를 사용하여 여러 파일을 수정해야 + 한다. (Perl이나 WSH/VB과 비교하여) 다운받기에 매우 작고 + 파일 생성 작업이 가능하여 awk를 선택했다. Brian Kernighan의 + <a href="http://cm.bell-labs.com/cm/cs/who/bwk/">http://cm.bell-labs.com/cm/cs/who/bwk/</a> 사이트에 + 컴파일된 Win32 실행파일 <a href="http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe">http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe</a>이 + 있다. 이름을 <code>awk95.exe</code> 대신 + <code>awk.exe</code>로 변경해야 한다.</p> + + <div class="note">Developer Studio IDE는 Tools 메뉴 Options... + Directories 탭의 (Developer Studio 7.0이라면 Projects + - VC++ Directories pane) Executable files 경로 목록에서만 + <code>awk.exe</code>를 찾는다. 이 목록에 <code>awk.exe</code> + 경로를 추가하고, 필요하다면 <code>PATH</code> 환경변수에도 + 추가한다.</div> + + <div class="note">Cygwin을 (<a href="http://www.cygwin.com/">http://www.cygwin.com/</a>) 사용한다면 + <code>gawk.exe</code>라는 이름으로 awk 도구가 있으며, + <code>awk.exe</code> 파일은 <code>gawk.exe</code> 파일의 + 심볼링크임을 주의하라. Windows 명령 프롬프트가 심볼링크를 + 인식하지 못하기때문에 InstallBin을 컴파일할때 실패한다. + 해결책은 cygwin에서 <code>awk.exe</code>를 삭제하고 + <code>gawk.exe</code> 이름을 <code>awk.exe</code>로 + 바꾼다.</div> + </li> + + <li> + <p>[선택적인] OpenSSL 라이브러리 (<code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>과 + <code>ab.exe</code>의 ssl 지원에 사용)</p> + <p><strong>주의: 강력한 암호화와 특허가 걸린 지적재산권을 + 전세계에 배포하는데는 상당한 제약이 있다.</strong> + OpenSSL은 미국 수출규제법이 규제하며 미국과 기타 지역에서 + 특허로 보호되는 지적재산권인 강력한 암호화를 포함한다. + Apache Software Foundation과 OpenSSL 프로젝트는 OpenSSL + 프로젝트가 제공하는 코드를 소유, 사용, 배포하는데 따른 + 법적 자문을 제공하지 않는다. <strong>직접 법률 상담을 + 받길 바란다. 당신 행동의 책임은 당신에게 있다.</strong></p> + + <p><code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>이나 (SSL을 지원하는 + <code>ab.exe</code>) abs 프로젝트를 컴파일하려면, OpenSSL을 + <a href="http://www.openssl.org/source/">http://www.openssl.org/source/</a>에서 다운받아서 + <code>srclib</code>의 <code>openssl</code>이라는 + 하위디렉토리에 설치해야 한다. <code>release</code>와 + <code>debug</code>로 아파치를 컴파일할때 사용하며 0.9.7 + 버전에 있는 특허가 걸린 기능을 사용하지 않는다면, 아래 + 컴파일 명령어를 사용한다:</p> + + <div class="example"><p><code> + perl Configure VC-WIN32<br /> + perl util\mkfiles.pl >MINFO<br /> + perl util\mk1mf.pl dll no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile<br /> + perl util\mk1mf.pl dll debug no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile.dbg<br /> + perl util\mkdef.pl 32 libeay no-asm no-mdc2 no-rc5 no-idea >ms\libeay32.def<br /> + perl util\mkdef.pl 32 ssleay no-asm no-mdc2 no-rc5 no-idea >ms\ssleay32.def<br /> + nmake<br /> + nmake -f makefile.dbg + </code></p></div> + + </li> + + <li> + <p>[선택적인] zlib 소스 (<code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>에 + 사용)</p> + <p>Zlib을 <code>srclib</code>의 <code>zlib</code>라는 + 하위디렉토리에 설치해야 하지만, 소스를 미리 컴파일할 + 필요는 없다. 컴파일 시스템은 이 압축소스를 + <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code> 모듈과 같이 컴파일한다. + Zlib은 <a href="http://www.gzip.org/zlib/">http://www.gzip.org/zlib/</a>에서 구할 수 있다 -- + <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>는 1.1.4 버전과 정상적으로 + 컴파일되었다.</p> + </li> + + </ul> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="commandbuild" id="commandbuild">명령행에서 컴파일하기</a></h2> + + + + <p>먼저 적당한 디렉토리에 아파치 배포본 압축을 푼다. 명령행 + 프롬프트를 열고 그 디렉토리로 <code>cd</code>한다.</p> + + <p><code>Makefile.win</code> 파일에 아파치 makefile 명령이 + 있다. Windows NT에서 <code>release</code>와 <code>debug</code> + 컴파일하는 명령어는 각각 다음과 같다:</p> + + <div class="example"><pre> +nmake /f Makefile.win _apacher + +nmake /f Makefile.win _apached + </pre></div> + + <p>두 명령어 모두 아파치를 컴파일한다. 후자는 결과파일에 + 디버깅 정보를 포함하여 버그를 찾고 문제를 추적하기 쉽게 + 한다.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="workspacebuild" id="workspacebuild">Developer Studio Workspace IDE에서 컴파일하기</a></h2> + + + + <p>VC++의 Visual Studio 개발 환경을 사용하여 아파치를 컴파일할 + 수도 있다. 과정을 쉽게 하려고 Visual Studio workspace + <code>Apache.dsw</code>를 제공한다. 이 workspace는 완전한 + 아파치 바이너리 배포본에 필요한 <code>.dsp</code> 프로젝트 + 목록을 담고있다. 또, 알맞은 순서로 컴파일하기위한 프로젝트간 + 의존성 정보도 포함한다.</p> + + <p><code>Apache.dsw</code> workspace를 열고 + <code>InstallBin</code>을 (<code>Release</code>나 + <code>Debug</code> 중 원하는 것을) Active Project로 선택한다. + <code>InstallBin</code>은 관련된 모든 프로젝트를 컴파일하고, + 컴파일된 실행파일과 dll을 옮기는 <code>Makefile.win</code>을 + 호출한다. <code>InstallBin</code>의 Settings, General 탭, + Build command line 항목을 수정하여 <code>INSTDIR=</code>을 + 변경할 수 있다. <code>INSTDIR=</code> 기본값은 + <code>/Apache2</code> 디렉토리이다. (설치하지않고) 테스트로 + 컴파일만 해보려면 대신 <code>BuildBin</code> 프로젝트를 + 사용한다.</p> + + <p><code>.dsp</code> 프로젝트 파일은 Visual C++ 6.0 형식이다. + Visual C++ 5.0 (97)에서도 이 파일을 사용할 수 있다. Visual + C++ 7.0 (.net)은 <code>Apache.dsw</code>와 <code>.dsp</code> + 파일들을 <code>Apache.sln</code>과 <code>.msproj</code> + 파일들로 변환한다. <code>.dsp</code> 소스파일을 수정하면 + 반드시 <code>.msproj</code> 파일로 다시 변환하라! 그냥 VC++ + 7.0 IDE에서 <code>Apache.dsw</code>를 다시 열기만 하면 된다.</p> + + <p>또, Visual C++ 7.0 (.net) 사용자는 Build 메뉴, Configuration + Manager 대화창에서 <code>Debug</code>와 <code>Release</code>의 + abs, <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>, <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code> + Solution modules 선택을 해제해야 한다. <code>srclib</code>에 + <code>openssl</code>이나 <code>zlib</code> 디렉토리가 있는 + 경우에만 <code>nmake</code>를 실행하거나 (이 모듈을 명시적으로 + 컴파일하는) IDE <code>BinBuild</code> 대상을 사용하여 모듈을 + 컴파일 할 수 있다.</p> + + <p>Export한 <code>.mak</code> 파일들이 혼란스럽지만, Visual + C++ 5.0 사용자가 <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>, abs (SSL을 지원하는 + ab), <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>를 컴파일할때 필요하다. + VC++ 7.0 (.net) 사용자에게도 <code>binenv</code> 보다 + <code>nmake</code>를 사용하면 컴파일이 더 빠르다. VC++ 5.0이나 + 6.0 IDE에서 전체 프로젝트를 컴파일하고, Project 메뉴의 Export + for all makefiles를 사용하라. 동적으로 자동 생성하는 대상을 + 모두 컴파일하고 올바른 의존성 정보를 얻기위해서는 먼저 + 프로젝트를 컴파일해야 한다. 다음 명령어를 사용하여 경로를 + 수정하면 어떤 경로에서도 컴파일할 수 있다:</p> + + <div class="example"><p><code> + perl srclib\apr\build\fixwin32mak.pl + </code></p></div> + + <p><code>httpd</code> 소스 <em>최상위</em> 디렉토리에서 + 명령어를 실행해야 한다. 현재 디렉토리와 하위디렉토리에 있는 + 모든 <code>.mak</code>와 <code>.dep</code> 프로젝트파일을 + 수정하고, <code>.dsp</code>를 고려하여 파일시간을 수정한다.</p> + + <p>프로젝트파일을 다듬어서 패치를 보낸다면, 프로젝트파일을 + Visual Studio 6.0 형식으로 만들어야 한다. 변경은 간단하고, + VC++ 5.0에서 7.0까지 모든 환경에서 인식하는 최소한의 컴파일 + 옵션과 링커 옵션을 사용해야 한다.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="projectcomponents" id="projectcomponents">프로젝트 구성요소</a></h2> + + + + <p><code>Apache.dsw</code> workspace와 <code>makefile.win</code> + <code>nmake</code> 스크립트는 다음 순서대로 아파치 서버 + <code>.dsp</code> 프로젝트를 컴파일한다:</p> + + <ol> + <li><code>srclib\apr\apr.dsp</code></li> + + <li><code>srclib\apr\libapr.dsp</code></li> + + <li><code>srclib\apr-util\uri\gen_uri_delims.dsp</code></li> + + <li><code>srclib\apr-util\xml\expat\lib\xml.dsp</code></li> + + <li><code>srclib\apr-util\aprutil.dsp</code></li> + + <li><code>srclib\apr-util\libaprutil.dsp</code></li> + + <li><code>srclib\pcre\dftables.dsp</code></li> + + <li><code>srclib\pcre\pcre.dsp</code></li> + + <li><code>srclib\pcre\pcreposix.dsp</code></li> + + <li><code>server\gen_test_char.dsp</code></li> + + <li><code>libhttpd.dsp</code></li> + + <li><code>Apache.dsp</code></li> + </ol> + + <p>또, <code>modules\</code> 하위디렉토리 아래 대부분의 + 모듈에는 프로젝트파일이 있다.</p> + + <p><code>support\</code> 디렉토리에는 아파치를 실행하는데 + 필요하지는 않지만, 관리자가 아파치를 검사하거나 암호파일과 + 로그파일을 관리하는데 사용할 추가 프로그램들의 프로젝트파일이 + 있다. Windows 전용 지원 프로그램은 <code>support\win32\</code> + 디렉토리에 따로 있다.</p> + + <ol> + <li><code>support\ab.dsp</code></li> + + <li><code>support\htdigest.dsp</code></li> + + <li><code>support\htpasswd.dsp</code></li> + + <li><code>support\logresolve.dsp</code></li> + + <li><code>support\rotatelogs.dsp</code></li> + + <li><code>support\win32\ApacheMonitor.dsp</code></li> + + <li><code>support\win32\wintty.dsp</code></li> + </ol> + + <p>아파치를 컴파일하면 server root 디렉토리에 설치해야 한다. + 기본값은 같은 디스크의 <code>\Apache2</code> 디렉토리이다.</p> + + <p>컴파일하고 모든 파일을 원하는 폴더 <em>dir</em>에 자동으로 + 설치하려면 다음 <code>nmake</code> 명령어중 하나를 사용한다:</p> + + <div class="example"><pre> +nmake /f Makefile.win installr INSTDIR=<em>dir</em> + +nmake /f Makefile.win installd INSTDIR=<em>dir</em> + </pre></div> + + <p><code>INSTDIR</code>의 <em>dir</em> 아규먼트는 설치디렉토리를 + 뜻한다. 생락하면 <code>\Apache2</code>에 아파치를 설치한다.</p> + + <p>다음과 같이 설치한다:</p> + + <ul> + <li><code><em>dir</em>\bin\Apache.exe</code> - 아파치 + 실행파일</li> + + <li><code><em>dir</em>\bin\ApacheMonitor.exe</code> - + 서비스 감시용 작업표시줄 아이콘 도구</li> + + <li><code><em>dir</em>\bin\htdigest.exe</code> - Digest + auth 암호파일 도구</li> + + <li><code><em>dir</em>\bin\htdbm.exe</code> - SDBM auth + 데이터베이스 암호파일 도구</li> + + <li><code><em>dir</em>\bin\htpasswd.exe</code> - Basic + auth 암호파일 도구</li> + + <li><code><em>dir</em>\bin\logresolve.exe</code> - 로그파일에서 + dns 이름을 찾는 도구</li> + + <li><code><em>dir</em>\bin\rotatelogs.exe</code> - 로그파일 + 순환 도구</li> + + <li><code><em>dir</em>\bin\wintty.exe</code> - 콘솔창 + 도구</li> + + <li><code><em>dir</em>\bin\libapr.dll</code> - Apache + Portable Runtime 공유 라이브러리</li> + + <li><code><em>dir</em>\bin\libaprutil.dll</code> - Apache + Utility Runtime 공유 라이브러리</li> + + <li><code><em>dir</em>\bin\libhttpd.dll</code> - Apache + Core 라이브러리</li> + + <li><code><em>dir</em>\modules\mod_*.so</code> - 읽어들일 + 수 있는 아파치 모듈</li> + + <li><code><em>dir</em>\conf</code> - 설정 디렉토리</li> + + <li><code><em>dir</em>\logs</code> - 비어있는 로그 + 디렉토리</li> + + <li><code><em>dir</em>\include</code> - C 언어 헤더파일</li> + + <li><code><em>dir</em>\lib</code> - 링크 라이브러리파일</li> + </ul> + + <h3><a name="projectcomponents-warn" id="projectcomponents-warn">개발중인 아파치 버전을 컴파일할때 경고</a></h3> + + + + <div class="note"><code>.dsp</code> 파일은 <code>release</code>마다 + 새로 만들어진다. 개발자의 시간낭비를 막기위해 + <code>.mak</code> 파일은 새로 만들지 않는다. 그러므로 + <code>NMAKE</code> 명령어를 사용하여 새로운 <code>.dsp</code> + 프로젝트파일을 컴파일할 수 없다. 프로젝트에서 직접 모든 + <code>.mak</code> 파일을 export해야 한다. Microsoft Developer + Studio 환경에서 컴파일한다면 이 작업이 필요없다.</div> + + <div class="note">또, makefile을 export하기 전에 <code>BuildBin</code> + 프로젝트를 (혹은 <code>_apacher</code>나 <code>_apached</code> + 명령행 대상) 컴파일하면 매우 도움이 된다. 컴파일중에 많은 + 파일이 자동으로 만들어진다. 전체를 컴파일해야만 정상적으로 + 컴파일할때 필요한 의존파일을 모두 만든다.</div> + + <p>배포용 <code>.mak</code> 파일을 만드려면 항상 + <code>.mak</code> (혹은 <code>.dep</code>)에서 Platform + SDK 등의 의존성을 점검하라. + <code>DevStudio\SharedIDE\bin\</code> (VC5)나 + <code>DevStudio\Common\MSDev98\bin\</code> (VC6) 디렉토리에는 + 모든 예외 목록이 담긴 <code>sysincl.dat</code> 파일이 + 있다. 이 파일에 의존성 정보를 추가한다 + (<code>sys/time.h</code>와 <code>sys\time.h</code>와 같이, + 경로는 슬래쉬를 사용한 것과 백슬래쉬를 사용한 것 모두를 + 추가한다). 배포할 <code>.mak</code> 파일에 현재 컴퓨터에만 + 해당하는 설치경로가 있다면 컴파일이 완전히 실패한다. + 그러므로 <code>srclib/apr/build/fixwin32mak.pl</code>을 + 실행해하여 <code>.mak</code> 파일에 있는 절대경로를 없애야 + 한다.</p> + + + + </div></div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/platform/win_compiling.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/win_compiling.html" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/windows.html b/rubbos/app/httpd-2.0.64/docs/manual/platform/windows.html new file mode 100644 index 00000000..a4e6fa16 --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/windows.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: windows.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: windows.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/windows.html.en b/rubbos/app/httpd-2.0.64/docs/manual/platform/windows.html.en new file mode 100644 index 00000000..8508075e --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/windows.html.en @@ -0,0 +1,754 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Using Apache with Microsoft Windows - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Using Apache with Microsoft Windows</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="../en/platform/windows.html" title="English"> en </a> | +<a href="../ko/platform/windows.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div> + + + <p>This document explains how to install, configure and run + Apache 2.0 under Microsoft Windows. If you find any bugs, or + wish to contribute in other ways, please use our <a href="http://httpd.apache.org/bug_report.html">bug reporting + page</a>.</p> + + <p>This document assumes that you are installing a binary + distribution of Apache. If you want to compile Apache yourself + (possibly to help with development or tracking down bugs), + see <a href="win_compiling.html">Compiling Apache for Microsoft + Windows</a>.</p> + + <p><strong>Because of the current versioning policies on Microsoft + Windows operating system families, this document assumes the + following:</strong></p> + <ul> + <li><strong>Windows NT:</strong> This means all versions of + Windows that are based on the Windows NT kernel. Includes Windows + NT, Windows 2000, Windows XP and Windows .Net Server 2003.</li> + <li><strong>Windows 9x:</strong> This means older, + consumer-oriented versions of Windows. Includes Windows 95 (also + OSR2), Windows 98 and Windows ME.</li> + </ul> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Operating System Requirements</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for Windows</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#inst">Installing Apache for Windows</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#cust">Customizing Apache for Windows</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#winsvc">Running Apache as a Service</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#wincons">Running Apache as a Console Application</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#test">Testing the Installation</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="req" id="req">Operating System Requirements</a></h2> + + + <p>The primary Windows platform for running Apache 2.0 is Windows + NT. The binary installer only works with the x86 family of + processors, such as Intel and AMD processors. Running Apache on + Windows 9x is not thoroughly tested, and it is never recommended on + production systems. + </p> + + <p>On all operating systems, TCP/IP networking must be installed + and working. If running on Windows 95, the Winsock 2 upgrade must + be installed. Winsock 2 for Windows 95 can be downloaded from <a href="http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp">here</a>. + </p> + + <p>On Windows NT 4.0, installing Service Pack 6 is strongly + recommended, as Service Pack 4 created known issues with TCP/IP + and Winsock integrity that were resolved in later Service Packs.</p> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="down" id="down">Downloading Apache for Windows</a></h2> + + + <p>Information on the latest versions of Apache can be found on the + web site of the Apache web server at + <a href="http://httpd.apache.org/download.cgi">http://httpd.apache.org/download.cgi</a>. + There you will find the current release, as well as more recent alpha + or beta test versions, and a list of HTTP and FTP mirrors from which + you can download the Apache web server. Please use a mirror near to + you for a fast and reliable download.</p> + + <p>For Windows installations you should download the version of + Apache for Windows with the <code>.msi</code> extension. This is a + single Microsoft Installer file, which contains a ready-to-run + version of Apache. There is a separate <code>.zip</code> file, + which contains only the source code. You can compile Apache + yourself with the Microsoft Visual C++ (Visual Studio) tools.</p> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="inst" id="inst">Installing Apache for Windows</a></h2> + + + <p>You need Microsoft Installer 1.2 or above for the installation + to work. On Windows 9x you can update your Microsoft Installer to + version 2.0 <a href="http://www.microsoft.com/downloads/release.asp?ReleaseID=32831">here</a> + and on Windows NT 4.0 and 2000 the version 2.0 update can be found + <a href="http://www.microsoft.com/downloads/release.asp?ReleaseID=32832">here</a>. + Windows XP does not need this update.</p> + + <p>Note that you cannot install two versions of Apache 2.0 on the + same computer with the binary installer. You can, however, install + a version of the 1.3 series <strong>and</strong> a version of the + 2.0 series on the same computer without problems. If you need to + have two different 2.0 versions on the same computer, you have to + <a href="win_compiling.html">compile and install Apache from the + source</a>.</p> + + <p>Run the Apache <code>.msi</code> file you downloaded above. The + installation will ask you for these things:</p> + + <ol> + <li><p><strong>Network Domain.</strong> Enter the DNS domain in which + your server is or will be registered in. For example, if your + server's full DNS name is <code>server.mydomain.net</code>, you would + type <code>mydomain.net</code> here.</p></li> + + <li><p><strong>Server Name.</strong> Your server's full DNS name. + From the example above, you would type <code>server.mydomain.net</code> + here.</p></li> + + <li><p><strong>Administrator's Email Address.</strong> Enter the + server administrator's or webmaster's email address here. This + address will be displayed along with error messages to the client + by default.</p></li> + + <li><p><strong>For whom to install Apache</strong> Select <code>for + All Users, on Port 80, as a Service - Recommended</code> if you'd + like your new Apache to listen at port 80 for incoming traffic. + It will run as a service (that is, Apache will run even if no one + is logged in on the server at the moment) Select <code>only for + the Current User, on Port 8080, when started Manually</code> if + you'd like to install Apache for your personal experimenting or + if you already have another WWW server running on port 80.</p></li> + + <li><p><strong>The installation type.</strong> Select <code>Typical</code> + for everything except the source code and libraries for module + development. With <code>Custom</code> you can specify what to + install. A full install will require about 13 megabytes of free + disk space. This does <em>not</em> include the size of your web + site(s).</p></li> + + <li><p><strong>Where to install.</strong> The default path is + <code>C:\Program Files\Apache Group</code> under which a directory + called <code>Apache2</code> will be created by default.</p></li> + </ol> + + <p>During the installation, Apache will configure the files in the + <code>conf</code> subdirectory to reflect the chosen installation + directory. However, if any of the configuration files in this + directory already exist, they will not be overwritten. Instead, the + new copy of the corresponding file will be left with the extension + <code>.default</code>. So, for example, if <code>conf\httpd.conf</code> + already exists, it will be renamed as <code>conf\httpd.conf.default</code>. + After the installation you should manually check to see what new + settings are in the <code>.default</code> file, and if necessary, + update your existing configuration file.</p> + + <p>Also, if you already have a file called <code>htdocs\index.html</code>, + it will not be overwritten (and no <code>index.html.default</code> + will be installed either). This means it should be safe to install + Apache over an existing installation, although you would have to + stop the existing running server before doing the installation, and + then start the new one after the installation is finished.</p> + + <p>After installing Apache, you must edit the configuration files + in the <code>conf</code> subdirectory as required. These files + will be configured during the installation so that Apache is ready + to be run from the directory it was installed into, with the + documents server from the subdirectory <code>htdocs</code>. There + are lots of other options which you should set before you really + start using Apache. However, to get started quickly, the files + should work as installed.</p> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="cust" id="cust">Customizing Apache for Windows</a></h2> + + + <p>Apache is configured by the files in the <code>conf</code> + subdirectory. These are the same files used to configure the Unix + version, but there are a few different directives for Apache on + Windows. See the <a href="../mod/directives.html">directive index</a> + for all the available directives.</p> + + <p>The main differences in Apache for Windows are:</p> + <ul> + <li><p>Because Apache for Windows is multithreaded, it does not + use a separate process for each request, as Apache does on Unix. + Instead there are usually only two Apache processes running: a + parent process, and a child which handles the requests. Within + the child process each request is handled by a separate thread. + </p> + + <p>The process management directives are also different:</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code>: + Like the Unix directive, this controls how many requests a single + child process will serve before exiting. However, unlike on Unix, + a single process serves all the requests at once, not just one. + If this is set, it is recommended that a very high number is + used. The recommended default, <code>MaxRequestsPerChild 0</code>, + causes the child process to never exit.</p> + + <div class="warning"><strong>Warning: The server configuration + file is reread when a new child process is started. If you have + modified <code>httpd.conf</code>, the new child may not start or + you may receive unexpected results.</strong></div> + + <p><code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code>: + This directive is new. It tells the server how many threads it + should use. This is the maximum number of connections the server + can handle at once, so be sure to set this number high enough for + your site if you get a lot of hits. The recommended default is + <code>ThreadsPerChild 50</code>.</p></li> + + <li><p>The directives that accept filenames as arguments must use + Windows filenames instead of Unix ones. However, because Apache + uses Unix-style names internally, you must use forward slashes, + not backslashes. Drive letters can be used; if omitted, the drive + with the Apache executable will be assumed.</p></li> + + <li><p>While filenames are generally case-insensitive on + Windows, URLs are still treated internally as case-sensitive + before they are mapped to the filesystem. For example, the + <code class="directive"><a href="../mod/core.html#location"><Location></a></code>, + <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>, and <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> directives all use + case-sensitive arguments. For this reason, it is particularly + important to use the <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> directive when attempting + to limit access to content in the filesystem, since this + directive applies to any content in a directory, regardless of + how it is accessed. If you wish to assure that only lowercase + is used in URLs, you can use something like:</p> + + <div class="example"><p><code> + RewriteEngine On<br /> + RewriteMap lowercase int:tolower<br /> + RewriteCond %{REQUEST_URI} [A-Z]<br /> + RewriteRule (.*) ${lowercase:$1} [R,L] + </code></p></div></li> + + <li><p>Apache for Windows contains the ability to load modules at + runtime, without recompiling the server. If Apache is compiled + normally, it will install a number of optional modules in the + <code>\Apache2\modules</code> directory. To activate these or + other modules, the new <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code> + directive must be used. For example, to activate the status + module, use the following (in addition to the status-activating + directives in <code>access.conf</code>):</p> + + <div class="example"><p><code> + LoadModule status_module modules/mod_status.so + </code></p></div> + + <p>Information on <a href="../mod/mod_so.html#creating">creating + loadable modules</a> is also available.</p></li> + + <li><p>Apache can also load ISAPI (Internet Server Application + Programming Interface) extensions (i.e. internet server + applications), such as those used by Microsoft IIS and other + Windows servers. <a href="../mod/mod_isapi.html">More information + is available</a>. Note that Apache <strong>cannot</strong> load + ISAPI Filters.</p></li> + + <li><p>When running CGI scripts, the method Apache uses to find + the interpreter for the script is configurable using the + <code class="directive"><a href="../mod/core.html#scriptinterpretersource">ScriptInterpreterSource</a></code> + directive.</p></li> + + <li><p>Since it is often difficult to manage files with names + like <code>.htaccess</code> in Windows, you may find it useful to + change the name of this per-directory configuration file using + the <code class="directive"><a href="../mod/core.html#accessfilename">AccessFilename</a></code> + directive.</p></li> + + <li><p>Any errors during Apache startup are logged into the + Windows event log when running on Windows NT. This mechanism + acts as a backup for those situations where Apache cannot even + access the normally used <code>error.log</code> file. You can + view the Windows event log by using the Event Viewer application + on Windows NT 4.0, and the Event Viewer MMC snap-in on newer + versions of Windows.</p> + + <div class="note"><strong>Note that there is no startup error logging on + Windows 9x because no Windows event log exists on those operating + systems.</strong></div></li> + </ul> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="winsvc" id="winsvc">Running Apache as a Service</a></h2> + + + <p>Apache can be run as a service on Windows NT. There is some + highly experimental support for similar behavior on Windows 9x.</p> + + <p>You can install Apache as a service automatically during the + installation. If you chose to install for all users, the + installation will create an Apache service for you. If you specify + to install for yourself only, you can manually register Apache as a + service after the installation. You have to be a member of the + Administrators group for the service installation to succeed.</p> + + <p>Apache comes with a utility called the Apache Service Monitor. + With it you can see and manage the state of all installed Apache + services on any machine on your network. To be able to manage an + Apache service with the monitor, you have to first install the + service (either automatically via the installation or manually). + </p> + + <p>You can install Apache as a Windows NT service as follows from + the command prompt at the Apache <code>bin</code> subdirectory:</p> + + <div class="example"><p><code> + httpd -k install + </code></p></div> + + <p>If you need to specify the name of the service you want to + install, use the following command. You have to do this if you + have several different service installations of Apache on your + computer.</p> + + <div class="example"><p><code> + httpd -k install -n "MyServiceName" + </code></p></div> + + <p>If you need to have specifically named configuration files for + different services, you must use this:</p> + + <div class="example"><p><code> + httpd -k install -n "MyServiceName" -f "c:\files\my.conf" + </code></p></div> + + <p>If you use the first command without any special parameters except + <code>-k install</code>, the service will be called <code>Apache2</code> + and the configuration will be assumed to be <code>conf\httpd.conf</code>. + </p> + + <p>Removing an Apache service is easy. Just use:</p> + + <div class="example"><p><code> + httpd -k uninstall + </code></p></div> + + <p>The specific Apache service to be uninstalled can be specified by using:</p> + + <div class="example"><p><code> + httpd -k uninstall -n "MyServiceName" + </code></p></div> + + <p>Normal starting, restarting and shutting down of an Apache + service is usually done via the Apache Service Monitor, by using + commands like <code>NET START Apache2</code> and <code>NET STOP + Apache2</code> or via normal Windows service management. Before + starting Apache as a service by any means, you should test the + service's configuration file by using:</p> + + <div class="example"><p><code> + httpd -n "MyServiceName" -t + </code></p></div> + + <p>You can control an Apache service by its command line switches, + too. To start an installed Apache service you'll use this:</p> + + <div class="example"><p><code> + httpd -k start + </code></p></div> + + <p>To stop an Apache service via the command line switches, use + this:</p> + + <div class="example"><p><code> + httpd -k stop + </code></p></div> + + <p>or</p> + + <div class="example"><p><code> + httpd -k shutdown + </code></p></div> + + <p>You can also restart a running service and force it to reread + its configuration file by using:</p> + + <div class="example"><p><code> + httpd -k restart + </code></p></div> + + <p>By default, all Apache services are registered to run as the + system user (the <code>LocalSystem</code> account). The + <code>LocalSystem</code> account has no privileges to your network + via any Windows-secured mechanism, including the file system, named + pipes, DCOM, or secure RPC. It has, however, wide privileges locally. + </p> + + <div class="warning"><strong>Never grant any network privileges to + the <code>LocalSystem</code> account! If you need Apache to be able + to access network resources, create a separate account for Apache as + noted below.</strong></div> + + <p>You may want to create a separate account for running Apache + service(s). Especially, if you have to access network resources + via Apache, this is strongly recommended.</p> + + <ol> + <li>Create a normal domain user account, and be sure to + memorize its password.</li> + + <li>Grant the newly-created user a privilege of <code>Log on + as a service</code> and <code>Act as part of the operating + system</code>. On Windows NT 4.0 these privileges are granted via + User Manager for Domains, but on Windows 2000 and XP you probably + want to use Group Policy for propagating these settings. You can + also manually set these via the Local Security Policy MMC snap-in. + </li> + + <li>Confirm that the created account is a member of the Users + group.</li> + + <li>Grant the account read and execute (RX) rights to all document + and script folders (<code>htdocs</code> and <code>cgi-bin</code> + for example).</li> + + <li>Grant the account change (RWXD) rights to the + Apache <code>logs</code> directory.</li> + + <li>Grant the account read and execute (RX) rights to the + <code>Apache.exe</code> binary executable.</li> + </ol> + + <div class="note">It is usually a good practice to grant the user the Apache + service runs as read and execute (RX) access to the whole Apache2 + directory, except the <code>logs</code> subdirectory, where the + user has to have at least change (RWXD) rights.</div> + + <p>If you allow the account to log in as a user and as a service, + then you can log on with that account and test that the account has the + privileges to execute the scripts, read the web pages, and that + you can start Apache in a console window. If this works, and you + have followed the steps above, Apache should execute as a service + with no problems.</p> + + <div class="note"><strong>Error code 2186</strong> is a good indication that + you need to review the "Log On As" configuration for the service, + since Apache cannot access a required network resource. Also, pay + close attention to the privileges of the user Apache is + configured to run as.</div> + + <p>When starting Apache as a service you may encounter an error + message from the Windows Service Control Manager. For example, + if you try to start Apache by using the Services applet in the + Windows Control Panel, you may get the following message:</p> + + <div class="example"><p><code> + Could not start the Apache2 service on \\COMPUTER <br /> + Error 1067; The process terminated unexpectedly. + </code></p></div> + + <p>You will get this generic error if there is any problem with + starting the Apache service. In order to see what is really causing + the problem you should follow the instructions for Running Apache + for Windows from the Command Prompt.</p> + + <p>There is some support for Apache on Windows 9x to behave in a + similar manner as a service on Windows NT. It is <strong>highly + experimental</strong>. It is not of production-class reliability, + and its future is not guaranteed. It can be mostly regarded as + a risky thing to play with - proceed with caution!</p> + + <p>There are some differences between the two kinds of services + you should be aware of:</p> + + <ul> + <li><p>Apache will attempt to start and if successful it will run + in the background. If you run the command</p> + + <div class="example"><p><code> + httpd -n "MyServiceName" -k start + </code></p></div> + + <p>via a shortcut on your desktop, for example, then if the + service starts successfully, a console window will flash up but + it immediately disappears. If Apache detects any errors on startup + such as incorrect entries in the httpd.conf configuration file, + the console window will remain visible. This will display an error + message which will be useful in tracking down the cause of the + problem.</p></li> + + <li><p>Windows 9x does not support <code>NET START</code> or + <code>NET STOP</code> commands. You must control the Apache + service on the command prompt via the <code>-k</code> switches. + </p></li> + + <li><p>Apache and Windows 9x offer no support for running Apache + as a specific user with network privileges. In fact, Windows 9x + offers no security on the local machine, either. This is the + simple reason because of which the Apache Software Foundation + never endorses use of a Windows 9x -based system as a public + Apache server. The primitive support for Windows 9x exists only + to assist the user in developing web content and learning the + Apache server, and perhaps as an intranet server on a secured, + private network.</p></li> + + </ul> + + <p>Once you have confirmed that Apache runs correctly as a + console application you can install, control and uninstall the + pseudo-service with the same commands as on Windows NT. You can + also use the Apache Service Monitor to manage Windows 9x + pseudo-services.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="wincons" id="wincons">Running Apache as a Console Application</a></h2> + + + <p>Running Apache as a service is usually the recommended way to + use it, but it is sometimes easier to work from the command line + (on Windows 9x running Apache from the command line is the + recommended way due to the lack of reliable service support.)</p> + + <p>To run Apache from the command line as a console application, + use the following command:</p> + + <div class="example"><p><code> + httpd + </code></p></div> + + <p>Apache will execute, and will remain running until it is stopped + by pressing Control-C.</p> + + <p>You can also run Apache via the shortcut Start Apache in Console + placed to <code>Start Menu --> Programs --> Apache HTTP Server + 2.0.xx --> Control Apache Server</code> during the installation. + This will open a console window and start Apache inside it. If you + don't have Apache installed as a service, the window will remain + visible until you stop Apache by pressing Control-C in the console + window where Apache is running in. The server will exit in a few + seconds. However, if you do have Apache installed as a service, the + shortcut starts the service. If the Apache service is running + already, the shortcut doesn't do anything.</p> + + <p>You can tell a running Apache to stop by opening another console + window and entering:</p> + + <div class="example"><p><code> + httpd -k shutdown + </code></p></div> + + <p>This should be preferred over pressing Control-C because this + lets Apache end any current operations and clean up gracefully.</p> + + <p>You can also tell Apache to restart. This forces it to reread + the configuration file. Any operations in progress are allowed to + complete without interruption. To restart Apache, use:</p> + + <div class="example"><p><code> + httpd -k restart + </code></p></div> + + <div class="note">Note for people familiar with the Unix version of Apache: + these commands provide a Windows equivalent to <code>kill -TERM + <em>pid</em></code> and <code>kill -USR1 <em>pid</em></code>. The + command line option used, <code>-k</code>, was chosen as a reminder + of the <code>kill</code> command used on Unix.</div> + + <p>If the Apache console window closes immediately or unexpectedly + after startup, open the Command Prompt from the Start Menu --> + Programs. Change to the folder to which you installed Apache, type + the command <code>apache</code>, and read the error message. Then + change to the logs folder, and review the <code>error.log</code> + file for configuration mistakes. If you accepted the defaults when + you installed Apache, the commands would be:</p> + + <div class="example"><p><code> + c: <br /> + cd "\Program Files\Apache Group\Apache2\bin" <br /> + httpd + </code></p></div> + + <p>Then wait for Apache to stop, or press Control-C. Then enter the + following:</p> + + <div class="example"><p><code> + cd ..\logs <br /> + more < error.log + </code></p></div> + + <p>When working with Apache it is important to know how it will + find the configuration file. You can specify a configuration file + on the command line in two ways:</p> + + <ul> + <li><p><code>-f</code> specifies an absolute or relative path to + a particular configuration file:</p> + + <div class="example"><p><code> + httpd -f "c:\my server files\anotherconfig.conf" + </code></p></div> + + <p>or</p> + + <div class="example"><p><code> + httpd -f files\anotherconfig.conf + </code></p></div></li> + + <li><p><code>-n</code> specifies the installed Apache service + whose configuration file is to be used:</p> + + <div class="example"><p><code> + httpd -n "MyServiceName" + </code></p></div> + </li> + </ul> + + <p>In both of these cases, the proper + <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> should be set in + the configuration file.</p> + + <p>If you don't specify a configuration file with <code>-f</code> + or <code>-n</code>, Apache will use the file name compiled into the + server, such as <code>conf\httpd.conf</code>. This built-in path + is relative to the installation directory. You can verify the compiled + file name from a value labelled as <code>SERVER_CONFIG_FILE</code> when + invoking Apache with the <code>-V</code> switch, like this:</p> + + <div class="example"><p><code> + httpd -V + </code></p></div> + + <p>Apache will then try to determine its <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> by trying the following, in this order:</p> + + <ol> + <li>A <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive + via the <code>-C</code> command line switch.</li> + + <li>The <code>-d</code> switch on the command line.</li> + + <li>Current working directory.</li> + + <li>A registry entry which was created if you did a binary + installation.</li> + + <li>The server root compiled into the server. This is <code> + /apache</code> by default, you can verify it by using <code> + apache -V</code> and looking for a value labelled as + <code>HTTPD_ROOT</code>.</li> + </ol> + + <p>During the installation, a version-specific registry key is + created in the Windows registry. The location of this key depends + on the type of the installation. If you chose to install Apache + for all users, the key is located under the + <code>HKEY_LOCAL_MACHINE</code> hive, like this (the version + numbers will of course vary between different versions of Apache: + </p> + + <div class="example"><p><code> + HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache\2.0.43 + </code></p></div> + + <p>Correspondingly, if you chose to install Apache for the current + user only, the key is located under the <code>HKEY_CURRENT_USER</code> + hive, the contents of which are dependent of the user currently + logged on:</p> + + <div class="example"><p><code> + HKEY_CURRENT_USER\SOFTWARE\Apache Group\Apache\2.0.43 + </code></p></div> + + <p>This key is compiled into the server and can enable you to test + new versions without affecting the current version. Of course, you + must take care not to install the new version in the same + directory as another version.</p> + + <p>If you did not do a binary install, Apache will in some + scenarios complain about the missing registry key. This warning can + be ignored if the server was otherwise able to find its + configuration file.</p> + + <p>The value of this key is the + <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directory which + contains the <code>conf</code> subdirectory. When Apache starts it + reads the <code>httpd.conf</code> file from that directory. If + this file contains a <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> + directive which contains a different directory from the one + obtained from the registry key above, Apache will forget the + registry key and use the directory from the configuration file. If + you copy the Apache directory or configuration files to a new + location it is vital that you update the + <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive in the + <code>httpd.conf</code> file to reflect the new location.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="test" id="test">Testing the Installation</a></h2> + + + <p>After starting Apache (either in a console window or as a + service) it will be listening on port 80 (unless you changed the + <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive in the + configuration files or installed Apache only for the current user). + To connect to the server and access the default page, launch a + browser and enter this URL:</p> + + <div class="example"><p><code> + http://localhost/ + </code></p></div> + + <p>Apache should respond with a welcome page and a link to the + Apache manual. If nothing happens or you get an error, look in the + <code>error.log</code> file in the <code>logs</code> subdirectory. + If your host is not connected to the net, or if you have serious + problems with your DNS (Domain Name Service) configuration, you + may have to use this URL:</p> + + <div class="example"><p><code> + http://127.0.0.1/ + </code></p></div> + + <p>If you happen to be running Apache on an alternate port, you need + to explicitly put that in the URL:</p> + + <div class="example"><p><code> + http://127.0.0.1:8080/ + </code></p></div> + + <p>Once your basic installation is working, you should configure it + properly by editing the files in the <code>conf</code> subdirectory. + Again, if you change the configuration of the Windows NT service + for Apache, first attempt to start it from the command line to + make sure that the service starts with no errors.</p> + + <p>Because Apache <strong>cannot</strong> share the same port with + another TCP/IP application, you may need to stop, uninstall or reconfigure + certain other services before running Apache. These conflicting + services include other WWW servers and some firewall implementations. + </p> + + </div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="../en/platform/windows.html" title="English"> en </a> | +<a href="../ko/platform/windows.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> +</body></html>
\ No newline at end of file diff --git a/rubbos/app/httpd-2.0.64/docs/manual/platform/windows.html.ko.euc-kr b/rubbos/app/httpd-2.0.64/docs/manual/platform/windows.html.ko.euc-kr new file mode 100644 index 00000000..cc46d62f --- /dev/null +++ b/rubbos/app/httpd-2.0.64/docs/manual/platform/windows.html.ko.euc-kr @@ -0,0 +1,688 @@ +<?xml version="1.0" encoding="EUC-KR"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="ko" xml:lang="ko"><head><!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Microsoft Windows에서 아파치 사용법 - Apache HTTP Server</title> +<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> +<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> +<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /> +<link href="../images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p> +<p class="apache">Apache HTTP Server Version 2.0</p> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> +<div id="path"> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Microsoft Windows에서 아파치 사용법</h1> +<div class="toplang"> +<p><span>가능한 언어: </span><a href="../en/platform/windows.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/windows.html" title="Korean"> ko </a></p> +</div> +<div class="outofdate">이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.</div> + + + <p>이 문서는 Microsoft Windows에서 아파치 2.0을 설치, 설정, + 실행하는 방법을 설명한다. 잘못된 부분이 있거나 다른 방법으로 + 도움을 주려면, <a href="http://httpd.apache.org/bug_report.html">버그 보고 + 페이지</a>를 사용하길 바란다.</p> + + <p>이 문서는 아파치 바이너리 배포본을 설치한다고 가정한다. + (아마도 개발 혹은 버그를 찾기위해) 직접 아파치를 컴파일하려면 + <a href="win_compiling.html">Microsoft Windows용 아파치 + 컴파일</a>을 참고하라.</p> + + <p><strong>현재 Microsoft Windows 운영체제군의 버전 정책상 + 이 문서는 다음과 같이 구분한다:</strong></p> + <ul> + <li><strong>Windows NT:</strong> Windows NT 커널을 기반으로 + 하는 모든 Windows 버전을 의미한다. Windows NT, Windows + 2000, Windows XP, Windows .Net Server 2003을 지칭한다.</li> + <li><strong>Windows 9x:</strong> 소비자 중심의 오래된 + Windows 버전을 뜻한다. Windows 95 (OSR2 포함), Windows + 98, Windows ME를 지칭한다.</li> + </ul> + + </div> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">운영체제 요구조건</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#down">Windows용 아파치 다운로드</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#inst">Windows용 아파치 설치하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#cust">Windows용 아파치 설정하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#winsvc">아파치를 Service로 실행하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#wincons">아파치를 콘솔 프로그램으로 실행하기</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#test">정상적으로 설치되었는지 검사하기</a></li> +</ul></div> +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="req" id="req">운영체제 요구조건</a></h2> + + + <p>아파치 2.0을 실행하기위한 기본 Windows 플래폼은 Windows + NT이다. 바이너리 설치프로그램은 Intel과 AMD와 같은 x86 개열 + 프로세서에서만 동작한다. 아파치는 Windows 9x에서 충분히 + 검사하지 않았기때문에 절대로 실제 서비스에 사용하지 않길 + 바란다. + </p> + + <p>운영체제에 설치한 TCP/IP 네트워크가 동작해야 한다. Windows + 95에서 실행한다면, Winsock 2 업그레이드를 설치해야 한다. + Windows 95용 Winsock 2는 <a href="http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp">여기</a>에서 + 다운받을 수 있다. + </p> + + <p>Windows NT 4.0을 사용한다면 서비스팩 4의 TCP/IP 문제와 + Winsock 문제가 다음 서비스팩에서 해결되었기때문에, 서비스팩 + 6을 설치하길 적극 권한다.</p> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="down" id="down">Windows용 아파치 다운로드</a></h2> + + + <p>아파치 웹서버 <a href="http://httpd.apache.org/download.cgi">http://httpd.apache.org/download.cgi</a>에서 + 아파치 최신 버전에 대한 정보를 얻을 수 있다. 여기에는 최신 + 발표판과 알파 혹은 베타 테스트버전과, 아파치 웹서버를 다운로드할 + 수 있는 HTTP 미러와 FTP 미러 목록이 있다. 빠르고 안정하게 + 다운받으려면 가까운 미러를 사용하길 바란다.</p> + + <p>Windows에 설치하려면 확장자가 <code>.msi</code>인 Windows용 + 아파치 버전을 다운받아야 한다. 이 파일은 막바로 실행할 수 + 있는 아파치를 저장한 Microsoft 설치파일이다. 따로 소스코드만 + 묶어둔 <code>.zip</code> 파일이 있다. Microsoft Visual C++ + (Visual Studio)을 사용하여 직접 아파치를 컴파일할 수도 있다.</p> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="inst" id="inst">Windows용 아파치 설치하기</a></h2> + + + <p>설치하려면 Microsoft Installer 1.2 이상 버전이 필요하다. + Windows 9x를 사용한다면 <a href="http://www.microsoft.com/downloads/release.asp?ReleaseID=32831">여기</a>에서 + Microsoft Installer를 2.0 버전으로 업그레이드할 수 있고, + Windows NT 4.0과 2000을 사용한다면 <a href="http://www.microsoft.com/downloads/release.asp?ReleaseID=32832">여기</a>에서 + 2.0 버전 업데이트를 구할 수 있다. Windows XP는 업데이트할 + 필요가 없다.</p> + + <p>바이너리 설치파일로는 같은 컴퓨터에 서로 다른 아파치 + 2.0 버전을 설치할 수 없음을 주의하라. 그러나 1.3 + 버전<strong>과</strong> 2.0 버전은 같은 컴퓨터에 아무 문제없이 + 설치할 수 있다. 같은 컴퓨터에 두가지 다른 2.0 버전을 설치하려면 + <a href="win_compiling.html">소스를 컴파일하여 아파치를 + 설치</a>해야 한다.</p> + + <p>위에서 다운받은 아파치 <code>.msi</code> 파일을 실행한다. + 설치할때 다음과 같은 것을 물어본다:</p> + + <ol> + <li><p><strong>네트워크 도메인 (Network Domain).</strong> + 등록된 서버의 DNS 도메인을 입력한다. 예를 들어, 서버의 + 전체 DNS 이름이 <code>server.mydomain.net</code>이라면 + 여기에 <code>mydomain.net</code>을 입력한다.</p></li> + + <li><p><strong>서버명 (Server Name).</strong> 서버의 전체 + DNS 이름. 위의 경우 여기에 <code>server.mydomain.net</code>을 + 입력한다.</p></li> + + <li><p><strong>관리자 전자우편 주소 (Administrator's Email + Address).</strong> 여기에 서버 관리자나 웹마스터의 전자우편 + 주소를 입력한다. 기본적으로 클라이언트에게 보내는 오류문에 + 이 주소를 기록한다.</p></li> + + <li><p><strong>사용자 대상 (For whom to install + Apache)</strong> 새로 설치하는 아파치가 80번 포트에서 + 요청을 기다리게 하려면 <code>for All Users, on Port 80, + as a Service - Recommended</code> (모든 사용자, 80번 포트, + service로 - 추천)를 선택한다. 아파치를 service로 실행한다 + (즉, 아파치는 서버에 로그인한 사람이 없어도 실행된다). + 개인적으로 테스트해보거나 이미 80번 포트를 사용하는 다른 + 웹서버가 있다면 <code>only for the Current User, on Port + 8080, when started Manually</code> (현재 사용자만, 8080번 + 포트, 직접 시작)를 선택한다.</p></li> + + <li><p><strong>설치 종류 (The installation type).</strong> + 모듈 개발에 필요한 소스코드와 라이브러리를 제외한 모든 + 것을 설치하려면 <code>Typical</code>을 선택한다. + <code>Custom</code>을 선택하면 설치할 내용을 지정할 수 + 있다. 전체 설치시 디스크에 빈 공간이 약 13 메가바이트 + 정도 필요하다. 이 수치는 웹사이트 크기를 <em>제외한</em> + 것이다.</p></li> + + <li><p><strong>설치 장소 (Where to install).</strong> + 기본 경로는 <code>C:\Program Files\Apache Group</code>이고, + 이곳에 <code>Apache2</code>라는 디렉토리를 만든다.</p></li> + </ol> + + <p>설치할 동안 아파치는 <code>conf</code> 하위디렉토리에 + 있는 파일들을 선택한 설치 디렉토리에 맞게 구성한다. 그러나 + 이 디렉토리에 설정파일이 이미 있다면 그대로 둔다. 대신, + 해당 파일의 새로운 복사본에 확장자 <code>.default</code>를 + 붙인다. 예를 들어, <code>conf\httpd.conf</code>가 이미 있다면 + <code>conf\httpd.conf.default</code>로 이름을 변경한다. + 설치후 <code>.default</code> 파일의 설정을 직접 살펴보고, + 필요하다면 기존 설정파일을 수정해야 한다.</p> + + <p>또, 이미 <code>htdocs\index.html</code>이라는 파일이 + 있다면 그대로 둔다 (<code>index.html.default</code>라고 + 복사하지도 않는다). 즉, 기존에 아파치가 설치되있더라도 안전하게 + 아파치를 새로 설치할 수 있다. 물론 설치하기 전에 서버를 + 중단하고, 설치후 새로운 서버를 시작해야 한다.</p> + + <p>아파치 설치후 필요하다면 <code>conf</code> 하위디렉토리에 + 있는 설정파일을 수정해야 한다. 파일은 아파치를 설치한 디렉토리의 + <code>htdocs</code> 하위디렉토리에 있는 문서를 서비스하도록 + 설정되있다. 실제로 아파치를 사용하기 전에 설정해야 할 옵션이 + 많다. 그러나 빨리 실행해볼 수 있도록 기본 설정파일로도 동작한다.</p> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="cust" id="cust">Windows용 아파치 설정하기</a></h2> + + + <p>아파치는 <code>conf</code> 하위디렉토리에 있는 파일로 + 설정한다. 이 파일은 유닉스용과 같지만, Windows용 아파치 + 특유의 지시어가 몇개 있다. 사용가능한 모든 지시어를 보려면 + <a href="../mod/directives.html">지시어 목록</a>을 참고하라.</p> + + <p>Windows용 아파치의 주된 차이점은:</p> + <ul> + <li><p>Windows용 아파치는 다중쓰레드 방식을 사용하기때문에, + 유닉스와 달리 요청마다 다른 프로세스를 사용하지 않는다. + 대신 아파치 프로세스는 항상, 부모 프로세스와 요청을 처리하는 + 자식 프로세스, 2개이다. 자식 프로세스에 있는 여러 쓰레드들이 + 요청들을 처리한다. + </p> + + <p>프로세스 관리 지시어도 다르다:</p> + + <p><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code>: 유닉스와 + 같이, 자식 프로세스가 요청을 얼마만큼 처리하고 죽을지를 + 조정한다. 그러나 유닉스와 달리 프로세스가 한번에 한 요청만을 + 처리하지않고 한번에 모든 요청을 서비스하기때문에, 설정한다면 + 매우 큰 값을 설정하길 권한다. 권장하는 기본값 + <code>MaxRequestsPerChild 0</code>을 사용하면 자식 프로세스는 + 죽지않고 영원히 요청을 서비스한다.</p> + + <div class="warning"><strong>경고: 자식 프로세스는 새로 + 시작할 때마다 서버설정파일을 새로 읽는다. + <code>httpd.conf</code>를 수정했다면, 자식 프로세스가 + 시작하지 않거나 예기치않은 결과가 발생할 수 있다.</strong></div> + + <p><code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code>: + 이 지시어는 새로 추가되었다. 이 지시어는 서버가 사용할 + 쓰레드 개수를 지정한다. 이 값이 서버가 한번에 처리할 수 + 있는 최대 연결개수이기때문에, 사이트에 접속량이 많다면 + 충분히 큰 값을 설정해야 한다. 권장하는 기본값은 + <code>ThreadsPerChild 50</code>이다.</p></li> + + <li><p>파일명을 아규먼트로 받는 지시어는 유닉스 파일명이 + 아닌 Windows 파일명을 사용해야 한다. 그러나 아파치 내부에서 + 유닉스식 이름을 사용하기때문에 백슬래쉬가 아닌 슬래쉬를 + 사용해야 한다. 드라이브 문자를 사용할 수 있다. 드라이브를 + 지정하지 않으면 아파치 실행파일이 있는 드라이브를 + 사용한다.</p></li> + + <li><p>Windows용 아파치는 서버를 다시 컴파일하지 않고 + 실행중에 모듈을 읽어들일 수 있다. 기본값으로 아파치를 + 컴파일하면 <code>\Apache2\modules</code> 디렉토리에 여러 + 선택가능한 모듈을 설치한다. 이 모듈 혹은 다른 모듈을 + 사용하려면 새로 생긴 <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code> 지시어를 사용한다. + 예를 들어, status 모듈을 사용한다면 + (<code>access.conf</code>에 status관련 지시어와 함께) + 아래와 같이 설정한다:</p> + + <div class="example"><p><code> + LoadModule status_module modules/mod_status.so + </code></p></div> + + <p><a href="../mod/mod_so.html#creating">읽어들일 수 있는 + 모듈 만들기</a>에 대한 정보도 있다.</p></li> + + <li><p>아파치는 Microsoft IIS와 다른 Windows 서버가 사용하는 + ISAPI (Internet Server Application Programming Interface) + 확장을 (즉, 인터넷 서버 프로그램) 읽어들일 수도 있다. + <a href="../mod/mod_isapi.html">더 자세한 정보가 있다</a>. + 아파치는 ISAPI 필터를 읽어들일 수 <strong>없음을</strong> + 주의하라.</p></li> + + <li><p>CGI 스크립트를 사용한다면 <code class="directive"><a href="../mod/core.html#scriptinterpretersource">ScriptInterpreterSource</a></code> 지시어를 + 사용하여 아파치가 스크립트의 인터프리터를 찾는 방법을 + 설정할 수 있다.</p></li> + + <li><p>Windows에서 <code>.htaccess</code>와 같은 파일명을 + 다루기 힘드므로, <code class="directive"><a href="../mod/core.html#accessfilename">AccessFilename</a></code> 지시어를 사용하여 + 디렉토리별 설정파일 이름을 변경하면 편하다.</p></li> + + <li><p>Windows NT라면 아파치 시작시 발생한 오류를 Windows + 이벤트 로그에 기록한다. 그래서 아파치가 보통 사용하는 + <code>error.log</code> 파일을 사용할 수 없는 경우에 대비한다. + Windows 이벤트 로그는 Windows NT 4.0에서는 이벤트 뷰어 + 프로그램으로, 최신 Windows 버전에서는 이벤트 뷰어 MMC + 스냅인에서 볼 수 있다.</p> + + <div class="note"><strong>Windows 9x에는 Windows 이벤트 로그가 없기때문에 + 시작시 발생한 오류를 기록하지 않는다.</strong></div></li> + </ul> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="winsvc" id="winsvc">아파치를 Service로 실행하기</a></h2> + + + <p>Windows NT에서는 아파치를 service로 실행할 수 있다. Windows + 9x에는 매우 실험적인 방법으로 비슷한 기능을 지원한다.</p> + + <p>설치시 자동으로 아파치를 service로 설치할 수 있다. "모든 + 사용자"를 선택하면, 아파치 service가 만들어진다. "현재 + 사용자만"을 선택하더라도 설치후 직접 아파치를 service로 + 등록할 수 있다. service를 설치하려면 Administrators 그룹의 + 구성원이어야 한다.</p> + + <p>아파치에는 Apache Service Monitor라는 도구가 있다. 이 + 도구를 사용하면 네트웍에 있는 다른 컴퓨터에 설치된 아파치 + 상태도 확인하고 관리할 수 있다. monitor로 아파치 service를 + 관리하려면 먼저 service를 (설치시 자동으로 혹은 직접) 설치해야 + 한다. + </p> + + <p>아파치 <code>bin</code> 하위디렉토리에서 명령행 프롬프트에 + 다음과 같이 입력하면 아파치를 Windows NT service로 설치한다:</p> + + <div class="example"><p><code> + apache -k install + </code></p></div> + + <p>설치할 service 이름을 지정하고 싶다면 다음 명령어를 사용한다. + 컴퓨터에 아파치가 여러개 설치되있다면 이름을 다르게 주어야 + 한다.</p> + + <div class="example"><p><code> + apache -k install -n "MyServiceName" + </code></p></div> + + <p>service가 사용할 설정파일을 직접 지정하려면 다음과 같이 + 한다:</p> + + <div class="example"><p><code> + apache -k install -n "MyServiceName" -f "c:\files\my.conf" + </code></p></div> + + <p><code>-k install</code> 외에 다른 파라미터를 사용하지 + 않으면, service 이름은 <code>Apache2</code>가 되고 설정파일은 + <code>conf\httpd.conf</code>가 된다. + </p> + + <p>아파치 service를 제거하기 쉽다. 간단히:</p> + + <div class="example"><p><code> + apache -k uninstall + </code></p></div> + + <p>다음과 같이 제거할 아파치 service를 지정할 수 있다:</p> + + <div class="example"><p><code> + apache -k uninstall -n "MyServiceName" + </code></p></div> + + <p>보통 아파치 service 시작, 재시작, 종료는 Apache Service + Monitor나 <code>NET START Apache2</code>, <code>NET STOP + Apache2</code> 같은 명령어 혹은 Windows 서비스 관리창에서 + 한다. 어떤 방법을 사용하든지 아파치 service를 시작하기 전에 + 설정파일을 검사해봐야 한다:</p> + + <div class="example"><p><code> + apache -n "MyServiceName" -t + </code></p></div> + + <p>명령행 옵션으로도 아파치 service를 조정할 수 있다. 설치한 + 아파치 serivce를 시작하려면:</p> + + <div class="example"><p><code> + apache -k start + </code></p></div> + + <p>명령행 옵션으로 아파치 service를 종료하려면:</p> + + <div class="example"><p><code> + apache -k stop + </code></p></div> + + <p>혹은</p> + + <div class="example"><p><code> + apache -k shutdown + </code></p></div> + + <p>실행중인 service를 재시작하여 설정파일을 다시 읽도록 + 할 수 있다:</p> + + <div class="example"><p><code> + apache -k restart + </code></p></div> + + <p>기본적으로 모든 아파치 service는 시스템 사용자 + (<code>LocalSystem</code> 계정) 권한으로 실행하도록 등록된다. + Windows 보안구조상 <code>LocalSystem</code> 계정은 파일시스템, + named pipes, DCOM, secure RPC 등 어떤 방법을 사용하든지 + 네트웍에 접근할 수 없다. 그러나 해당 컴퓨터에서는 많은 권한을 + 가진다. + </p> + + <div class="warning"><strong><code>LocalSystem</code> 계정에게 + 네트웍 권한을 절대로 주지 마라! 아파치가 네트웍 자원에 접근해야 + 한다면, 아래에서 설명하는 방법으로 아파치를 위한 별도의 + 계정을 만들어라.</strong></div> + + <p>아파치 service를 실행하기위한 별도의 계정을 만들 수도 + 있다. 특히 아파치가 네트웍 자원에 접근해야 한다면 이 방법을 + 강력히 권한다.</p> + + <ol> + <li>일반 도메인 사용자 계정을 만들고 암호를 기억하라.</li> + + <li>새로 만든 계정에 <code>서비스로 로그온</code>와 + <code>운영 체제의 일부로 활동</code> 권한을 + 부여한다. Windows NT 4.0에서는 User Manager for Domains에서 + 권한을 부여할 수 있고, Windows 2000과 XP에서는 아마도 + "그룹 정책"을 사용해야 한다. "로컬 보안 설정" MMC + 스냅인에서 직접 설정해줄 수도 있다. + </li> + + <li>새로 만든 계정이 Users 그룹에 속하는지 확인한다.</li> + + <li>모든 문서와 스크립트 폴더에 (예를 들어 + <code>htdocs</code>와 <code>cgi-bin</code>) 대해 읽기 및 + 실행 (RX) 권한을 부여한다.</li> + + <li>아파치 <code>logs</code> 디렉토리에 수정 (RWXD) 권한을 + 부여한다.</li> + + <li><code>Apache.exe</code> 실행파일에 읽기 및 실행 (RX) + 권한을 부여한다.</li> + </ol> + + <div class="note">아파치 service를 실행하는 사용자에게 최소한 수정 (RWXD) + 권한이 필요한 <code>logs</code> 하위디렉토리를 제외하고 + Apache2 디렉토리 전체에 읽기 및 실행 (RX) 권한을 부여하는 + 것이 좋다.</div> + + <p>계정에 "로컬 로그온"과 "서비스로 로그온" 권한이 있다면, + 그 계정으로 로그온하여 계정이 스크립트를 실행하고 웹페이지를 + 읽으며 콘솔창에서 아파치를 시작할 수 있는지 검사해볼 수 + 있다. 여기서 문제가 없다면 아파치를 service로 실행해도 문제가 + 없다.</p> + + <div class="note"><strong>Error code 2186</strong>은 아파치가 필요한 + 네트웍 자원에 접근할 수 없다는 말로 service의 "로그온" + 설정을 확인하라. 또, 아파치를 실행하는 계정의 권한을 + 살펴봐라.</div> + + <p>아파치를 service로 실행하면 Windows Service Control + Manager에서 오류문을 볼 수 있다. 예를 들어, 제어판에서 + "서비스"를 사용하여 아파치를 시작하는 경우 다음과 같은 문구가 + 나올 수 있다:</p> + + <div class="example"><p><code> + Could not start the Apache2 service on \\COMPUTER <br /> + Error 1067; The process terminated unexpectedly. + </code></p></div> + + <p>아파치 service를 시작할때 문제가 있으면 일반적인 이런 + 오류가 나온다. 실제 어디가 문제인지 알려면 아파치를 콘솔 + 프로그램으로 실행해보라.</p> + + <p>Windows 9x에서 아파치는 Windows NT의 service와 비슷한 + 방법을 지원한다. 그러나 <strong>매우 실험적인</strong> 기능이다. + 실제 서비스에 사용할만큼 안정적이지 않고 앞으로 개선될지 + 보장할 수도 없다. 위험하므로 혹시나 사용한다면 주의해서 + 사용해야 한다!</p> + + <p>두가지 service의 중요한 차이점은 다음과 같다:</p> + + <ul> + <li><p>아파치가 성공적으로 시작하면 배경에서 실행한다. + 예를 들어, 데스크탑에 바로가기를 만들어서 다음 명령을 + 실행하는 경우,</p> + + <div class="example"><p><code> + apache -n "MyServiceName" -k start + </code></p></div> + + <p>service가 성공적으로 시작하면 콘솔창이 생겼다가 금방 + 사라진다. httpd.conf 설정파일에 잘못된 내용이 있는 등 + 아파치 시작시 오류가 발생하면 콘솔창을 계속 보인다. 콘솔창은 + 문제의 원인을 파악하는데 도움을 주는 오류문을 보여준다.</p></li> + + <li><p>Windows 9x는 <code>NET START</code>와 <code>NET + STOP</code> 명령어를 지원하지 않는다. 명령프롬프트에서 + <code>-k</code> 옵션을 사용하여 아파치 service를 조정해야 + 한다. + </p></li> + + <li><p> + 아파치와 Windows 9x는 네트웍 권한을 가진 특정 사용자로 + 아파치를 실행하지 못한다. 사실 Windows 9x는 보안을 제공하지도 + 않는다. 이것이 바로 Apache Software Foundation이 Windows + 9x 시스템을 공개 웹서버로 사용하길 권하지 않는 이유다. + 사용자가 웹 컨텐츠를 개발하고 아파치 서버 학습을 돕기위해, + 아니면 안전한 사설 네트웍에 위치할 인트라넷 서버를 위해, + Windows 9x를 지원할 뿐이다.</p></li> + + </ul> + + <p>아파치가 콘솔 프로그램으로 동작함을 확인하였다면 Windows + NT에서와 같은 명령어로 가상 service를 설치, 조절, 제거할 + 수 있다. 또, Apache Service Monitor를 사용하여 Windows 9x + 가상 service를 관리할 수 있다.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="wincons" id="wincons">아파치를 콘솔 프로그램으로 실행하기</a></h2> + + + <p>일반적으로 아파치를 service로 실행하길 권한다. 그러나 + 명령행에서 실행하는게 편한 경우가 있다 (Windows 9x에서는 + service를 안정적으로 지원하지 않기때문에 명령행에서 아파치를 + 실행하는 방법을 권한다).</p> + + <p>아파치를 콘솔 프로그램으로 실행하려면, 명령행에서 다음 + 명령어를 사용한다:</p> + + <div class="example"><p><code> + apache + </code></p></div> + + <p>아파치는 Control-C를 눌러서 정지할 때까지 실행된다.</p> + + <p>또, <code>시작 메뉴 --> 프로그램 --> Apache HTTP + Server 2.0.xx --> Control Apache Server</code>에 설치된 + Start Apache in Console 바로가기로 아파치를 실행할 수 있다. + 바로가기를 실행하면 콘솔창을 열고 그 안에서 아파치를 실행한다. + 아파치를 service로 설치하지 않았다면, 아파치를 실행하는 + 콘솔창에서 Control-C를 눌러 아파치를 중단할때까지 창이 떠있다. + 이 경우 서버는 몇초안에 종료한다. 그러나, 아파치를 service로 + 설치하였다면 바로가기는 service를 시작한다. 아파치 service가 + 이미 실행중이라면 바로가기는 아무일도 하지 않는다.</p> + + <p>다른 콘솔창을 열고 다음과 같이 입력하여 실행중인 아파치를 + 종료할 수 있다:</p> + + <div class="example"><p><code> + apache -k shutdown + </code></p></div> + + <p>이 방법은 아파치가 현재 작업을 마치고 점잖게 종료할 수 + 있기때문에 Control-C 보다 낫다.</p> + + <p>또, 아파치를 재시작할 수 있다. 이 경우 설정파일을 다시 + 읽는다. 진행중인 작업을 중간에 끊지않고 완료한다. 아파치를 + 재시작하려면:</p> + + <div class="example"><p><code> + apache -k restart + </code></p></div> + + <div class="note">유닉스용 아파치에 익숙한 사람을 위해: 이 명령어는 + <code>kill -TERM <em>pid</em></code>나 <code>kill -USR1 + <em>pid</em></code>의 Windows판이다. 명령행 옵션 + <code>-k</code>는 유닉스 <code>kill</code> 명령어 이름을 + 본따 지었다.</div> + + <p>아파치 콘솔창이 즉시 혹은 시작후 갑자기 닫치면 시작 메뉴 + --> 프로그램의 명령 프롬프트를 실행한다. 아파치를 설치한 + 폴더로 가서 <code>apache</code> 명령어를 실행해보고 발생한 + 오류문을 살펴본다. 그리고 logs 폴더로 가서, 설정파일이 + 잘못되었는지 <code>error.log</code> 파일을 살펴본다. 아파치를 + 설치할때 기본값을 사용했다면 다음과 같다:</p> + + <div class="example"><p><code> + c: <br /> + cd "\Program Files\Apache Group\Apache2\bin" <br /> + apache + </code></p></div> + + <p>아파치가 정지할 때까지 기다리거나 Control-C를 누른다. + 그리고 다음과 같이 입력한다:</p> + + <div class="example"><p><code> + cd ..\logs <br /> + more < error.log + </code></p></div> + + <p>아파치를 다룰때 아파치가 어떻게 설정파일을 찾는지 아는 + 것이 중요하다. 두가지 방법으로 명령행에서 설정파일을 지정할 + 수 있다:</p> + + <ul> + <li><p><code>-f</code>는 설정파일의 절대경로 혹은 상대경로를 + 지정한다:</p> + + <div class="example"><p><code> + apache -f "c:\my server files\anotherconfig.conf" + </code></p></div> + + <p>혹은</p> + + <div class="example"><p><code> + apache -f files\anotherconfig.conf + </code></p></div></li> + + <li><p><code>-n</code>은 아파치 service를 선택하고, 해당 + service의 설정파일을 사용한다:</p> + + <div class="example"><p><code> + apache -n "MyServiceName" + </code></p></div> + </li> + </ul> + + <p>두 경우 모두 설정파일이 적절한 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>를 지정해야 한다.</p> + + <p><code>-f</code>나 <code>-n</code>으로 설정파일을 지정하지 + 않으면, 아파치는 <code>conf\httpd.conf</code>와 같이 서버에 + 컴파일된 파일명을 사용한다. 이 기본 경로는 설치 디렉토리에 + 상대적이다. 다음과 같이 <code>-V</code> 옵션으로 아파치를 + 실행하면 <code>SERVER_CONFIG_FILE</code>이란 항목에서 서버가 + 사용할 설정파일을 알 수 있다:</p> + + <div class="example"><p><code> + apache -V + </code></p></div> + + <p>아파치는 다음 순서대로 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>를 찾는다:</p> + + <ol> + <li><code>-C</code> 명령행 옵션에 사용한 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> 지시어.</li> + + <li><code>-d</code> 명령행 옵션.</li> + + <li>현재 작업 디렉토리.</li> + + <li>바이너리 설치를 했다면 설치할때 만든 registry 항목.</li> + + <li>서버에 컴파일된 server root. 기본값은 + <code>/apache</code>이고, <code>apache -V</code>를 실행하면 + <code>HTTPD_ROOT</code>라는 항목에서 확인할 수 있다.</li> + </ol> + + <p>설치할때 윈도우즈 레지스트리에 버전 특유의 레지스트리 + 키를 만든다. 키의 위치는 설치 종류에 따라 다르다. install + Apache for all users를 선택하였다면 + <code>HKEY_LOCAL_MACHINE</code> 아래에 다음과 같은 키를 + 만든다 (물론 버전번호는 아파치 버전마다 다르다): + </p> + + <div class="example"><p><code> + HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache\2.0.43 + </code></p></div> + + <p>"모든 사용자"를 대상으로 아파치를 설치하였다면 + <code>HKEY_CURRENT_USER</code> 아래 키가 생긴다. 내용은 + 현재 로그온한 사용자에 따라 다르다:</p> + + <div class="example"><p><code> + HKEY_CURRENT_USER\SOFTWARE\Apache Group\Apache\2.0.43 + </code></p></div> + + <p>키 이름이 서버에 컴파일되기때문에 현재 버전을 건드리지않고 + 새로운 버전을 설치하여 테스트해볼 수 있다. 물론 새 버전을 + 다른 버전과 같은 디렉토리에 설치하지않도록 주의해야 한다.</p> + + <p>바이너리 설치를 하지 않은 경우 아파치는 레지스트리 키가 + 없다고 불평할 수 있다. 서버가 다른 방법으로 설정파일을 찾을 + 수 있다면 이 경고를 무시해도 된다.</p> + + <p>키의 값은 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> + 디렉토리이며, 이 디렉토리에 <code>conf</code>라는 하위디렉토리가 + 있다. 아파치를 시작하면 이 하위디렉토리에서 + <code>httpd.conf</code> 파일을 읽는다. 이 파일에 나오는 + <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> 지시어가 + 레지스트리 키에 나온 디렉토리와 다르다면, 아파치는 레지스트리에서 + 얻은 값을 무시하고 앞으로 설정파일에 나온 디렉토리를 사용한다. + 아파치 디렉토리나 설정파일을 다른 장소로 복사하면 반드시 + <code>httpd.conf</code> 파일에 있는 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> 지시어를 그 위치로 + 수정하라.</p> + + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> +<div class="section"> +<h2><a name="test" id="test">정상적으로 설치되었는지 검사하기</a></h2> + + + <p>(콘솔창이나 service를 통해) 아파치를 시작하면 (설정파일의 + <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> 지시어를 + 수정하거나 아파치를 "현재 사용자만" 대상으로 설치하지 않는 + 경우) 80번 포트를 기다린다. 브라우저를 시작하고 URL을 입력하여 + 서버의 기본 페이지에 접근하다:</p> + + <div class="example"><p><code> + http://localhost/ + </code></p></div> + + <p>아파치는 아파치 설명서 링크가 있는 환영페이지를 보여줘야 + 한다. 아무 일도 일어나지 않거나 오류가 나오면, <code>logs</code> + 하위디렉토리에 있는 <code>error.log</code> 파일을 살펴봐라. + 호스트가 네트웍에 연결되있지 않거나 DNS (Domain Name Service) + 설정에 문제가 있다면 다음 URL을 사용해야 한다:</p> + + <div class="example"><p><code> + http://127.0.0.1/ + </code></p></div> + + <p>기본 설치가 동작하면 <code>conf</code> 하위디렉토리에 + 있는 파일을 적절히 설정한다. 또, Windows NT 아파치 service + 설정을 수정한 경우 먼저 명령행에서 아파치를 시작하여 오류가 + 발생하지않는지 확인해야 한다.</p> + + <p>아파치가 다른 TCP/IP 프로그램과 같은 포트를 공유할 수 + <strong>없기때문에</strong> 아파치를 시작하기 전에 다른 + 서비스를 중단, 제거, 재설정해야 할지도 모른다. 다른 웹서버나 + 특정 방화벽 서버스와 충돌할 수 있다. + </p> + + </div></div> +<div class="bottomlang"> +<p><span>가능한 언어: </span><a href="../en/platform/windows.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="../ko/platform/windows.html" title="Korean"> ko </a></p> +</div><div id="footer"> +<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="../mod/">모듈</a> | <a href="../mod/directives.html">지시어들</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">용어</a> | <a href="../sitemap.html">사이트맵</a></p></div> +</body></html>
\ No newline at end of file |