diff options
Diffstat (limited to '')
| -rw-r--r-- | docs/manual/stopping.html | 29 | ||||
| -rw-r--r-- | docs/manual/stopping.html.de | 288 | ||||
| -rw-r--r-- | docs/manual/stopping.html.en | 264 | ||||
| -rw-r--r-- | docs/manual/stopping.html.es | 297 | ||||
| -rw-r--r-- | docs/manual/stopping.html.fr.utf8 | 305 | ||||
| -rw-r--r-- | docs/manual/stopping.html.ja.utf8 | 279 | ||||
| -rw-r--r-- | docs/manual/stopping.html.ko.euc-kr | 235 | ||||
| -rw-r--r-- | docs/manual/stopping.html.tr.utf8 | 273 |
8 files changed, 1970 insertions, 0 deletions
diff --git a/docs/manual/stopping.html b/docs/manual/stopping.html new file mode 100644 index 0000000..0f37598 --- /dev/null +++ b/docs/manual/stopping.html @@ -0,0 +1,29 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: stopping.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: stopping.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: stopping.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: stopping.html.fr.utf8 +Content-Language: fr +Content-type: text/html; charset=UTF-8 + +URI: stopping.html.ja.utf8 +Content-Language: ja +Content-type: text/html; charset=UTF-8 + +URI: stopping.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: stopping.html.tr.utf8 +Content-Language: tr +Content-type: text/html; charset=UTF-8 diff --git a/docs/manual/stopping.html.de b/docs/manual/stopping.html.de new file mode 100644 index 0000000..4a13cc4 --- /dev/null +++ b/docs/manual/stopping.html.de @@ -0,0 +1,288 @@ +<?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="de" xml:lang="de"><head> +<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Beenden und Neustarten - Apache HTTP Server Version 2.4</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 rel="stylesheet" type="text/css" href="./style/css/prettify.css" /> +<script src="./style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<link href="./images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="./mod/">Module</a> | <a href="./mod/directives.html">Direktiven</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">Glossar</a> | <a href="./sitemap.html">Seitenindex</a></p> +<p class="apache">Apache HTTP Server Version 2.4</p> +<img alt="" src="./images/feather.png" /></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/">Dokumentation</a> > <a href="./">Version 2.4</a></div><div id="page-content"><div id="preamble"><h1>Beenden und Neustarten</h1> +<div class="toplang"> +<p><span>Verfgbare Sprachen: </span><a href="./de/stopping.html" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Franais"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> +<div class="outofdate">Diese bersetzung ist mglicherweise + nicht mehr aktuell. Bitte prfen Sie die englische Version auf + die neuesten nderungen.</div> + + <p>Dieses Dokument umfasst das Beenden und Neustarten des + Apache auf Unix-hnlichen Systemen. Anwender von Windows NT, 2000 + und XP sollten <a href="platform/windows.html#winsvc">Betreiben + des Apache als Dienst</a> lesen, whrend hingegen Anwender von + Windows 9x sowie ME <a href="platform/windows.html#wincons">Betreiben + des Apache als Konsolenanwendung</a> lesen sollten, um mehr Informationen + zur Handhabung des Apache auf diesen Systemen zu erhalten.</p> +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#introduction">Einleitung</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#term">Beenden</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#graceful">Unterbrechungsfreier Neustart</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#hup">Neustarten</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#race">Anhang: Signale und Wettkampfsituationen</a></li> +</ul><h3>Siehe auch</h3><ul class="seealso"><li><code class="program"><a href="./programs/httpd.html">httpd</a></code></li><li><code class="program"><a href="./programs/apachectl.html">apachectl</a></code></li><li><a href="#comments_section">Kommentare</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="introduction" id="introduction">Einleitung</a></h2> + + <p>Um den Apache zu stoppen oder neu zu starten, mssen Sie + ein Signal an den laufenden <code class="program"><a href="./programs/httpd.html">httpd</a></code>-Prozess senden. Es gibt + zwei Mglichkeiten, diese Signale zu senden. Zum einen knnen + Sie den Unix-Befehl <code>kill</code> verwenden, um den Prozessen + direkt Signale zu senden. Sie werden feststellen, dass auf Ihrem + System mehrere <code class="program"><a href="./programs/httpd.html">httpd</a></code>-Programme laufen. Sie sollten + jedoch nicht jedem dieser Prozesse ein Signal senden, sondern nur dem + Elternprozess, dessen PID im <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> steht. Das heit, Sie + sollten es niemals ntig haben, einem anderen Prozess, als dem + Elternprozess, ein Signal zu senden. Es gibt drei Signale, die Sie an den + Elternprozess senden knnen: <code><a href="#term">TERM</a></code>, + <code><a href="#hup">HUP</a></code> und + <code><a href="#graceful">USR1</a></code>, die nachfolgend beschrieben + werden.</p> + + <p>Um dem Elternprozess ein Signal zu senden, verwenden Sie einen + Befehl wie z.B.:</p> + + <div class="example"><p><code>kill -TERM `cat /usr/local/apache2/logs/httpd.pid`</code></p></div> + + <p>Die zweite Methode, dem <code class="program"><a href="./programs/httpd.html">httpd</a></code>-Prozess zu + signalisieren, ist die Verwendung der <code>-k</code>-Befehlszeilenoptionen + <code>stop</code>, <code>restart</code> und <code>graceful</code>, wie + unten beschrieben. Dies sind Argumente des <code class="program"><a href="./programs/httpd.html">httpd</a></code>-Programms, es wird jedoch + empfohlen, sie unter Verwendung des Steuerskripts <code class="program"><a href="./programs/apachectl.html">apachectl</a></code> zu senden, welches diese + an <code class="program"><a href="./programs/httpd.html">httpd</a></code> durchreicht.</p> + + <p>Nachdem Sie <code class="program"><a href="./programs/httpd.html">httpd</a></code> signalisiert haben, knnen Sie + dessen Fortschritt beobachten, indem Sie eingeben:</p> + + <div class="example"><p><code>tail -f /usr/local/apache2/logs/error_log</code></p></div> + + <p>Passen Sie diese Beispiele entsprechend Ihren <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code>- und <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code>-Einstellungen an.</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="term" id="term">Beenden</a></h2> + + <dl><dt>Signal: TERM</dt> + <dd><code>apachectl -k stop</code></dd> + </dl> + + <p>Das Senden des <code>TERM</code>- oder <code>stop</code>-Signals an + den Elternprozess veranlasst diesen, sofort zu versuchen, alle seine + Kindprozesse zu beenden. Es kann einige Sekunden dauern, bis alle + Kindprozesse komplett beendet sind. Danach beendet sich der Elternprozess + selbst. Alle gerade bearbeiteten Anfragen werden abgebrochen. + Es werden keine weiteren Anfragen mehr bedient.</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="graceful" id="graceful">Unterbrechungsfreier Neustart</a></h2> + + <dl><dt>Signal: USR1</dt> + <dd><code>apachectl -k graceful</code></dd> + </dl> + + <p>Das <code>USR1</code>- oder <code>graceful</code>-Signal + veranlasst den Elternprozess, die Kinder <em>anzuweisen</em>, sich + nach Abschlu ihrer momentanen bearbeiteten Anfrage zu beenden + (oder sich sofort zu beenden, wenn sie gerade keine Anfrage bedienen). + Der Elternprozess liest seine Konfigurationsdateien erneut ein und + ffnet seine Logdateien neu. Wenn ein Kindprozess stirbt, + ersetzt der Elternprozess ihn durch ein Kind der neuen + Konfigurations-<em>Generation</em>. Dieses beginnt sofort damit, + neue Anfragen zu bedienen.</p> + + <div class="note">Auf bestimmten Plattformen, welche kein <code>USR1</code> + fr einen unterbrechungsfreien Neustart erlauben, kann ein + alternatives Signal verwendet werden (wie z.B. + <code>WINCH</code>). Der Befehl <code>apachectl graceful</code> + sendet das jeweils richtige Signal fr Ihre Platform.</div> + + <p>Der Code ist dafr ausgelegt, stets die MPM-Direktiven + zur Prozesssteuerung zu beachten, so dass die Anzahl der Prozesse + und Threads, die zur Bedienung der Clients bereitstehen, whrend + des Neustarts auf die entsprechenden Werte gesetzt werden. + Weiterhin wird <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> + auf folgende Art und Weise interpretiert: Wenn nach einer Sekunde + nicht mindestens <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> + neue Kindprozesse erstellt wurden, dann werden, um den Durchsatz zu + beschleunigen, entsprechend weitere erstellt. Auf diese Weise versucht + der Code sowohl die Anzahl der Kinder entsprechend der Serverlast + anzupassen als auch Ihre Wnsche hinsichtlich des Parameters + <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> zu + bercksichtigen.</p> + + <p>Benutzer von <code class="module"><a href="./mod/mod_status.html">mod_status</a></code> werden feststellen, + dass die Serverstatistiken <strong>nicht</strong> auf Null + zurckgesetzt werden, wenn ein <code>USR1</code> gesendet + wurde. Der Code wurde so geschrieben, dass sowohl die Zeit minimiert + wird, in der der Server nicht in der Lage ist, neue Anfragen zu + bedienen (diese werden vom Betriebssystem in eine Warteschlange + gestellt, so dass sie auf keinen Fall verloren gehen) als auch + Ihre Parameter zur Feinabstimmung bercksichtigt werden. + Um dies zu erreichen, muss die <em>Statustabelle</em> (Scoreboard), + die dazu verwendet wird, alle Kinder ber mehrere Generationen + zu verfolgen, erhalten bleiben.</p> + + <p>Das Statusmodul benutzt auerdem ein <code>G</code>, um + diejenigen Kinder zu kennzeichen, die noch immer Anfragen bedienen, + welche gestartet wurden, bevor ein unterbrechungsfreier Neustart + veranlat wurde.</p> + + <p>Derzeit gibt es keine Mglichkeit fr ein + Log-Rotationsskript, das <code>USR1</code> verwendet, sicher + festzustellen, dass alle Kinder, die in ein vor dem Neustart + geffnetes Log schreiben, beendet sind. Wir schlagen vor, dass + Sie nach dem Senden des Signals <code>USR1</code> eine angemessene + Zeitspanne warten, bevor Sie das alte Log anfassen. Wenn beispielsweise + die meisten Ihrer Zugriffe bei Benutzern mit niedriger Bandbreite + weniger als 10 Minuten fr eine vollstndige Antwort + bentigen, dann knnten Sie 15 Minuten warten, bevor Sie auf + das alte Log zugreifen.</p> + + <div class="note">Wenn Ihre Konfigurationsdatei Fehler enthlt, whrend + Sie einen Neustart anweisen, dann wird Ihr Elternprozess nicht neu starten, + sondern sich mit einem Fehler beenden. Im Falle eines unterbrechungsfreien + Neustarts lt er die Kinder weiterlaufen, wenn er sich beendet. + (Dies sind die Kinder, die sich "sanft beenden", indem sie ihre letzte + Anfrage erledigen.) Das verursacht Probleme, wenn Sie versuchen, + den Server neu zu starten -- er ist nicht in der Lage, sich an die Ports zu + binden, an denen er lauschen soll. Bevor Sie einen Neustart + durchfhren, knnen Sie die Syntax der Konfigurationsdateien + mit dem Befehlszeilenargument <code>-t</code> berprfen + (siehe auch <code class="program"><a href="./programs/httpd.html">httpd</a></code>). Das garantiert + allerdings nicht, dass der Server korrekt starten wird. Um sowohl die + Syntax als auch die Semantik der Konfigurationsdateien zu prfen, + knnen Sie versuchen, <code class="program"><a href="./programs/httpd.html">httpd</a></code> als nicht-root-Benutzer + zu starten. Wenn dabei keine Fehler auftreten, wird er versuchen, seine + Sockets und Logdateien zu ffnen und fehlschlagen, da er nicht root + ist (oder weil sich der gegenwrtig laufende <code class="program"><a href="./programs/httpd.html">httpd</a></code> + bereits diese Ports gebunden hat). Wenn er aus einem anderen Grund + fehlschlgt, dann liegt wahrscheinlich ein Konfigurationsfehler vor. + Der Fehler sollte behoben werden, bevor der unterbrechungsfreie Neustart + angewiesen wird.</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="hup" id="hup">Neustarten</a></h2> + + <dl><dt>Signal: HUP</dt> + <dd><code>apachectl -k restart</code></dd> + </dl> + + <p>Das Senden des Signals <code>HUP</code> oder <code>restart</code> + veranlat den Elternprozess, wie bei <code>TERM</code> alle seine + Kinder zu beenden. Der Elternprozess beendet sich jedoch nicht. Er liest + seine Konfigurationsdateien neu ein und ffnet alle Logdateien + erneut. Dann erzeugt er einen neuen Satz Kindprozesse und setzt die + Bedienung von Zugriffen fort.</p> + + <p>Benutzer von <code class="module"><a href="./mod/mod_status.html">mod_status</a></code> werden feststellen, dass + die Serverstatistiken auf Null gesetzt werden, wenn ein <code>HUP</code> + gesendet wurde.</p> + + <div class="note">Wenn Ihre Konfigurationsdatei einen Fehler enthlt, + whrend Sie einen Neustart anweisen, dann wird Ihr Elternprozess + nicht neu starten, sondern sich mit einem Fehler beenden. Lesen Sie oben, + wie Sie das vermeiden knnen.</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="race" id="race">Anhang: Signale und Wettkampfsituationen</a></h2> + + <p>Vor der Version 1.2b9 des Apache existierten verschiedene + <em>Wettkampfsituationen</em> (race conditions), die den Neustart und + die Signale beeinflut haben. (Einfach erklrt ist eine + Wettkampfsituation ein zeitabhngiges Problem - wenn + etwas zum falschen Zeitpunkt erfolgt oder Dinge in der falschen + Reihenfolge passieren, ist unerwartetes Verhalten die Folge. Wenn die + gleichen Dinge zur richtigen Zeit geschehen, funktioniert alles korrekt.) + Bei Architekturen mit dem "richtigen" Funktionsumfang + haben wir so viele eliminiert wie wir nur konnten. Dennoch + sollte beachtet werden, dass noch immer Wettkampfsituationen auf + bestimmten Architekturen existieren.</p> + + <p>Bei Architekturen, die ein <code class="directive"><a href="./mod/mpm_common.html#scoreboardfile">ScoreBoardFile</a></code> auf Platte verwenden, + besteht die Gefahr, dass die Statustabelle beschdigt wird. + Das kann zu "bind: Address already in use" ("bind: Adresse wird + bereits verwendet", nach einem <code>HUP</code>) oder "long lost + child came home!" ("Der verlorene Sohn ist heimgekehrt", nach einem + <code>USR1</code>) fhren. Ersteres ist ein schwerer Fehler, + wrend letzteres lediglich bewirkt, dass der Server einen Eintrag + in der Statustabelle verliert. So kann es ratsam sein, unterbrechungsfreie + Neustarts zusammen mit einem gelegentlichen harten Neustart zu verwenden. + Diese Probleme lassen sich nur sehr schwer umgehen, aber + glcklicherweise bentigen die meisten Architekturen keine + Statustabelle in Form einer Datei. Bitte lesen Sie fr Architekturen, + die sie bentigen, die Dokumentation zu <code class="directive"><a href="./mod/mpm_common.html#scoreboardfile">ScoreBoardFile</a></code>.</p> + + <p>Alle Architekturen haben in jedem Kindprozess eine kleine + Wettkampfsituation, welche die zweite und nachfolgende Anfragen + einer persistenten HTTP-Verbindung (KeepAlive) umfat. Der Prozess + kann nach dem Lesen der Anfragezeile aber vor dem Lesen der Anfrage-Header + enden. Es existiert eine Korrektur, die fr 1.2 zu spt kam. + Theoretisch sollte das kein Problem darstellen, da + der KeepAlive-Client derartige Ereignisse aufgrund von + Netzwerk-Latenzzeiten und Auszeiten des Servers erwarten sollte. + In der Praxis scheint keiner von beiden beeinflut zu werden + -- in einem Testfall wurde der Server zwanzig mal + pro Sekunde neu gestartet, whrend Clients das Angebot abgegrast + haben, ohne kaputte Bilder oder leere Dokumente zu erhalten.</p> +</div></div> +<div class="bottomlang"> +<p><span>Verfgbare Sprachen: </span><a href="./de/stopping.html" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Franais"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Kommentare</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/stopping.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2019 The Apache Software Foundation.<br />Lizenziert unter der <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="./mod/">Module</a> | <a href="./mod/directives.html">Direktiven</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">Glossar</a> | <a href="./sitemap.html">Seitenindex</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file diff --git a/docs/manual/stopping.html.en b/docs/manual/stopping.html.en new file mode 100644 index 0000000..8ba19bf --- /dev/null +++ b/docs/manual/stopping.html.en @@ -0,0 +1,264 @@ +<?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> +<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Stopping and Restarting Apache HTTP Server - Apache HTTP Server Version 2.4</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 rel="stylesheet" type="text/css" href="./style/css/prettify.css" /> +<script src="./style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p> +<p class="apache">Apache HTTP Server Version 2.4</p> +<img alt="" src="./images/feather.png" /></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.4</a></div><div id="page-content"><div id="preamble"><h1>Stopping and Restarting Apache HTTP Server</h1> +<div class="toplang"> +<p><span>Available Languages: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Franais"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> + + <p>This document covers stopping and restarting Apache HTTP Server on + Unix-like systems. Windows NT, 2000 and XP users should see + <a href="platform/windows.html#winsvc">Running httpd as a + Service</a> and Windows 9x and ME users should see <a href="platform/windows.html#wincons">Running httpd as a + Console Application</a> for information on how to control + httpd on those platforms.</p> +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#introduction">Introduction</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#term">Stop Now</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#graceful">Graceful Restart</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#hup">Restart Now</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#gracefulstop">Graceful Stop</a></li> +</ul><h3>See also</h3><ul class="seealso"><li><code class="program"><a href="./programs/httpd.html">httpd</a></code></li><li><code class="program"><a href="./programs/apachectl.html">apachectl</a></code></li><li><a href="invoking.html">Starting</a></li><li><a href="#comments_section">Comments</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="introduction" id="introduction">Introduction</a></h2> + + <p>In order to stop or restart the Apache HTTP Server, you must send a signal to + the running <code class="program"><a href="./programs/httpd.html">httpd</a></code> processes. There are two ways to + send the signals. First, you can use the unix <code>kill</code> + command to directly send signals to the processes. You will + notice many <code class="program"><a href="./programs/httpd.html">httpd</a></code> executables running on your system, + but you should not send signals to any of them except the parent, + whose pid is in the <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code>. That is to say you + shouldn't ever need to send signals to any process except the + parent. There are four signals that you can send the parent: + <code><a href="#term">TERM</a></code>, + <code><a href="#graceful">USR1</a></code>, + <code><a href="#hup">HUP</a></code>, and + <code><a href="#gracefulstop">WINCH</a></code>, which + will be described in a moment.</p> + + <p>To send a signal to the parent you should issue a command + such as:</p> + +<div class="example"><p><code>kill -TERM `cat /usr/local/apache2/logs/httpd.pid`</code></p></div> + + <p>The second method of signaling the <code class="program"><a href="./programs/httpd.html">httpd</a></code> processes + is to use the <code>-k</code> command line options: <code>stop</code>, + <code>restart</code>, <code>graceful</code> and <code>graceful-stop</code>, + as described below. These are arguments to the <code class="program"><a href="./programs/httpd.html">httpd</a></code> binary, but we recommend that + you send them using the <code class="program"><a href="./programs/apachectl.html">apachectl</a></code> control script, which + will pass them through to <code class="program"><a href="./programs/httpd.html">httpd</a></code>.</p> + + <p>After you have signaled <code class="program"><a href="./programs/httpd.html">httpd</a></code>, you can read about + its progress by issuing:</p> + +<div class="example"><p><code>tail -f /usr/local/apache2/logs/error_log</code></p></div> + + <p>Modify those examples to match your <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code> and <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> settings.</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="term" id="term">Stop Now</a></h2> + +<dl><dt>Signal: TERM</dt> +<dd><code>apachectl -k stop</code></dd> +</dl> + + <p>Sending the <code>TERM</code> or <code>stop</code> signal to + the parent causes it to immediately attempt to kill off all of its + children. It may take it several seconds to complete killing off + its children. Then the parent itself exits. Any requests in + progress are terminated, and no further requests are served.</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="graceful" id="graceful">Graceful Restart</a></h2> + +<dl><dt>Signal: USR1</dt> +<dd><code>apachectl -k graceful</code></dd> +</dl> + + <p>The <code>USR1</code> or <code>graceful</code> signal causes + the parent process to <em>advise</em> the children to exit after + their current request (or to exit immediately if they're not + serving anything). The parent re-reads its configuration files and + re-opens its log files. As each child dies off the parent replaces + it with a child from the new <em>generation</em> of the + configuration, which begins serving new requests immediately.</p> + + <p>This code is designed to always respect the process control + directive of the MPMs, so the number of processes and threads + available to serve clients will be maintained at the appropriate + values throughout the restart process. Furthermore, it respects + <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> in the + following manner: if after one second at least <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> new children have not + been created, then create enough to pick up the slack. Hence the + code tries to maintain both the number of children appropriate for + the current load on the server, and respect your wishes with the + <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> + parameter.</p> + + <p>Users of <code class="module"><a href="./mod/mod_status.html">mod_status</a></code> + will notice that the server statistics are <strong>not</strong> + set to zero when a <code>USR1</code> is sent. The code was + written to both minimize the time in which the server is unable + to serve new requests (they will be queued up by the operating + system, so they're not lost in any event) and to respect your + tuning parameters. In order to do this it has to keep the + <em>scoreboard</em> used to keep track of all children across + generations.</p> + + <p>The status module will also use a <code>G</code> to indicate + those children which are still serving requests started before + the graceful restart was given.</p> + + <p>At present there is no way for a log rotation script using + <code>USR1</code> to know for certain that all children writing + the pre-restart log have finished. We suggest that you use a + suitable delay after sending the <code>USR1</code> signal + before you do anything with the old log. For example if most of + your hits take less than 10 minutes to complete for users on + low bandwidth links then you could wait 15 minutes before doing + anything with the old log.</p> + + <div class="note"> + <p>When you issue a restart, a syntax check is first run, to + ensure that there are no errors in the configuration files. + If your configuration file has errors in it, you will get an + error message about that syntax error, and the server will refuse to + restart. This avoids the situation where the server halts and then + cannot restart, leaving you with a non-functioning server.</p> + + <p>This still will not + guarantee that the server will restart correctly. To check the + semantics of the configuration files as well as the syntax, you + can try starting <code class="program"><a href="./programs/httpd.html">httpd</a></code> as a non-root user. If there + are no errors it will attempt to open its sockets and logs and fail + because it's not root (or because the currently running + <code class="program"><a href="./programs/httpd.html">httpd</a></code> already has those ports bound). If it fails + for any other reason then it's probably a config file error and the error + should be fixed before issuing the graceful restart.</p></div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="hup" id="hup">Restart Now</a></h2> + +<dl><dt>Signal: HUP</dt> +<dd><code>apachectl -k restart</code></dd> +</dl> + + <p>Sending the <code>HUP</code> or <code>restart</code> signal to + the parent causes it to kill off its children like in + <code>TERM</code>, but the parent doesn't exit. It re-reads its + configuration files, and re-opens any log files. Then it spawns a + new set of children and continues serving hits.</p> + + <p>Users of <code class="module"><a href="./mod/mod_status.html">mod_status</a></code> + will notice that the server statistics are set to zero when a + <code>HUP</code> is sent.</p> + +<div class="note">As with a graceful restart, a syntax check is run before the +restart is attempted. If your configuration file has errors in it, the +restart will not be attempted, and you will receive notification of the +syntax error(s).</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="gracefulstop" id="gracefulstop">Graceful Stop</a></h2> + +<dl><dt>Signal: WINCH</dt> +<dd><code>apachectl -k graceful-stop</code></dd> +</dl> + + <p>The <code>WINCH</code> or <code>graceful-stop</code> signal causes + the parent process to <em>advise</em> the children to exit after + their current request (or to exit immediately if they're not + serving anything). The parent will then remove its <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> and cease listening on + all ports. The parent will continue to run, and monitor children + which are handling requests. Once all children have finalised + and exited or the timeout specified by the <code class="directive"><a href="./mod/mpm_common.html#gracefulshutdowntimeout">GracefulShutdownTimeout</a></code> has been + reached, the parent will also exit. If the timeout is reached, + any remaining children will be sent the <code>TERM</code> signal + to force them to exit.</p> + + <p>A <code>TERM</code> signal will immediately terminate the + parent process and all children when in the "graceful" state. However + as the <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> will + have been removed, you will not be able to use + <code>apachectl</code> or <code>httpd</code> to send this signal.</p> + + <div class="note"><p>The <code>graceful-stop</code> signal allows you to run multiple + identically configured instances of <code class="program"><a href="./programs/httpd.html">httpd</a></code> at the + same time. This is a powerful feature when performing graceful + upgrades of httpd, however it can also cause deadlocks and race + conditions with some configurations.</p> + + <p>Care has been taken to ensure that on-disk files such as lock files + (<code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code>) and Unix socket files + (<code class="directive"><a href="./mod/mod_cgid.html#scriptsock">ScriptSock</a></code>) contain the server + PID, and should coexist without problem. However, if a configuration + directive, third-party module or persistent CGI utilises any other on-disk + lock or state files, care should be taken to ensure that multiple running + instances of <code class="program"><a href="./programs/httpd.html">httpd</a></code> do not clobber each other's files.</p> + + <p>You should also be wary of other potential race conditions, such as + using <code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code> style piped logging. Multiple running + instances of <code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code> attempting to rotate the same + logfiles at the same time may destroy each other's logfiles.</p></div> +</div></div> +<div class="bottomlang"> +<p><span>Available Languages: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Espaol"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Franais"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/stopping.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2019 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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file diff --git a/docs/manual/stopping.html.es b/docs/manual/stopping.html.es new file mode 100644 index 0000000..0cdd842 --- /dev/null +++ b/docs/manual/stopping.html.es @@ -0,0 +1,297 @@ +<?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="es" xml:lang="es"><head> +<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Iniciar y Parar el servidor Apache - Servidor HTTP Apache Versin 2.4</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 rel="stylesheet" type="text/css" href="./style/css/prettify.css" /> +<script src="./style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<link href="./images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="./mod/">Mdulos</a> | <a href="./mod/directives.html">Directivas</a> | <a href="http://wiki.apache.org/httpd/FAQ">Preguntas Frecuentes</a> | <a href="./glossary.html">Glosario</a> | <a href="./sitemap.html">Mapa del sitio web</a></p> +<p class="apache">Versin 2.4 del Servidor HTTP Apache</p> +<img alt="" src="./images/feather.png" /></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/">Servidor HTTP</a> > <a href="http://httpd.apache.org/docs/">Documentacin</a> > <a href="./">Versin 2.4</a></div><div id="page-content"><div id="preamble"><h1>Iniciar y Parar el servidor Apache</h1> +<div class="toplang"> +<p><span>Idiomas disponibles: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" title="Espaol"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Franais"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div> +<div class="outofdate">Esta traduccin podra estar + obsoleta. Consulte la versin en ingls de la + documentacin para comprobar si se han producido cambios + recientemente.</div> + + <p>Este documento explica como iniciar y parar el servidor Apache + en sistemas tipo Unix. Los usuarios de Windows NT, 2000 y XP + deben consultar la seccin <a href="platform/windows.html#winsvc">Ejecutar Apache como un + servicio</a> y los usuario de Windows 9x y ME deben consultar <a href="platform/windows.html#wincons">Ejecutar Apache como una + Aplicacin de Consola</a> para obtener informacin + sobre como controlar Apache en esas plataformas.</p> +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#introduction">Introduccin</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#term">Parar Apache</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#graceful">Reinicio Graceful</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#hup">Reiniciar Apache</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#race">Apndice: seales y race conditions</a></li> +</ul><h3>Consulte tambin</h3><ul class="seealso"><li><a href="programs/httpd.html">httpd</a></li><li><a href="programs/apachectl.html">apachectl</a></li><li><a href="#comments_section">Comentarios</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="introduction" id="introduction">Introduccin</a></h2> + + <p>Para parar y reiniciar Apache, hay que enviar la seal + apropiada al proceso padre <code>httpd</code> que se est + ejecutando. Hay dos maneras de enviar estas seales. En + primer lugar, puede usar el comando de Unix <code>kill</code> que + enva seales directamente a los procesos. Puede que + tenga varios procesos <code>httpd</code> ejecutandose en su + sistema, pero las seales deben enviarse solamente al proceso + padre, cuyo pid est especificado en la directiva <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code>. Esto quiere decir que no + debe necesitar enviar seales a ningn proceso excepto + al proceso padre. Hay tres seales que puede enviar al + proceso padre: <code><a href="#term">TERM</a></code>, <code><a href="#hup">HUP</a></code>, y <code><a href="#graceful">USR1</a></code>, que van a ser descritas a + continuacin.</p> + + <p>Para enviar una seal al proceso padre debe escribir un + comando como el que se muestra en el ejemplo:</p> + +<div class="example"><p><code>kill -TERM `cat /usr/local/apache2/logs/httpd.pid`</code></p></div> + + <p>La segunda manera de enviar seales a los procesos + <code>httpd</code> es usando las opciones de lnea de + comandos <code>-k</code>: <code>stop</code>, <code>restart</code>, + y <code>graceful</code>, como se muestra ms abajo. Estas + opciones se le pueden pasar al binario <a href="programs/httpd.html">httpd</a>, pero se recomienda que se + pasen al script de control <a href="programs/apachectl.html">apachectl</a>, que a su vez los + pasar a <code>httpd</code>.</p> + + <p>Despus de haber enviado las seales que desee a + <code>httpd</code>, puede ver como progresa el proceso + escribiendo:</p> + +<div class="example"><p><code>tail -f /usr/local/apache2/logs/error_log</code></p></div> + + <p>Modifique estos ejemplos para que coincidan con la + configuracin que tenga especificada en las directivas + <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code> y <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> en su fichero principal de + configuracin.</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="term" id="term">Parar Apache</a></h2> + +<dl><dt>Seal: TERM</dt> +<dd><code>apachectl -k stop</code></dd> +</dl> + + <p>Enviar las seales <code>TERM</code> o <code>stop</code> + al proceso padre hace que se intenten eliminar todos los procesos + hijo inmediatamente. Esto puede tardar algunos minutos. Una vez + que hayan terminado todos los procesos hijo, terminar el + proceso padre. Cualquier peticin en proceso terminar + inmediatanmente, y ninguna peticin posterior ser + atendida.</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="graceful" id="graceful">Reinicio Graceful</a></h2> + +<dl><dt>Seal: USR1</dt> +<dd><code>apachectl -k graceful</code></dd> +</dl> + + <p>Las seales <code>USR1</code> o <code>graceful</code> + hacen que el proceso padre <em>indique</em> a sus hijos que + terminen despus de servir la peticin que estn + atendiendo en ese momento (o de inmediato si no estn + sirviendo ninguna peticin). El proceso padre lee de nuevo + sus ficheros de configuracin y vuelve a abrir sus ficheros + log. Conforme cada hijo va terminando, el proceso padre lo va + sustituyendo con un hijo de una nueva <em>generacin</em> con + la nueva configuracin, que empeciezan a servir peticiones + inmediatamente.</p> + + <div class="note">En algunas plataformas que no permiten usar + <code>USR1</code> para reinicios graceful, puede usarse una + seal alternativa (como <code>WINCH</code>). Tambien puede + usar <code>apachectl graceful</code> y el script de control + enviar la seal adecuada para su plataforma.</div> + + <p>Apache est diseado para respetar en todo momento la + directiva de control de procesos de los MPM, as como para + que el nmero de procesos y hebras disponibles para servir a + los clientes se mantenga en los valores adecuados durante el + proceso de reinicio. An ms, est diseado + para respetar la directiva <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> de la siguiente + manera: si despus de al menos un segundo el nuevo hijo de la + directiva <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> + no ha sido creado, entonces crea los suficientes para se atienda + el trabajo que queda por hacer. As, se intenta mantener + tanto el nmero de hijos adecuado para el trabajo que el + servidor tenga en ese momento, como respetar la configuracin + determinada por los parmetros de la directiva + <code class="directive">StartServers</code>.</p> + + <p>Los usuarios del mdulo <code class="module"><a href="./mod/mod_status.html">mod_status</a></code> + notarn que las estadsticas del servidor + <strong>no</strong> se ponen a cero cuando se usa la seal + <code>USR1</code>. Apache fue escrito tanto para minimizar el + tiempo en el que el servidor no puede servir nuevas peticiones + (que se pondrn en cola por el sistema operativo, de modo que + se no se pierda ningn evento), como para respetar sus + parmetros de ajuste. Para hacer esto, tiene que guardar el + <em>scoreboard</em> usado para llevar el registro de los procesos + hijo a travs de las distintas generaciones.</p> + + <p>El mod_status tambin usa una <code>G</code> para indicar + que esos hijos estn todava sirviendo peticiones + previas al reinicio graceful.</p> + + <p>Actualmente no existe ninguna manera de que un script con un + log de rotacin usando <code>USR1</code> sepa con seguridad + que todos los hijos que se registraron en el log con anterioridad + al reinicio han terminado. Se aconseja que se use un retardo + adecuado despus de enviar la seal <code>USR1</code> + antes de hacer nada con el log antiguo. Por ejemplo, si la mayor + parte las visitas que recibe de usuarios que tienen conexiones de + baja velocidad tardan menos de 10 minutos en completarse, entoces + espere 15 minutos antes de hacer nada con el log antiguo.</p> + + <div class="note">Si su fichero de configuracin tiene errores cuando + haga el reinicio, entonces el proceso padre no se reinciciar + y terminar con un error. En caso de un reinicio graceful, + tambin dejar a los procesos hijo ejecutandose mientras + existan. (Estos son los hijos de los que se est saliendo de + forma graceful y que estn sirviendo sus ltimas + peticiones.) Esto provocar problemas si intenta reiniciar el + servidor -- no ser posible conectarse a la lista de puertos + de escucha. Antes de reiniciar, puede comprobar que la sintaxis de + sus ficheros de configuracion es correcta con la opcin de + lnea de comandos <code>-t</code> (consulte <a href="programs/httpd.html">httpd</a>). No obstante, esto no + garantiza que el servidor se reinicie correctamente. Para + comprobar que no hay errores en los ficheros de + configuracin, puede intentar iniciar <code>httpd</code> con + un usuario diferente a root. Si no hay errores, intentar + abrir sus sockets y logs y fallar porque el usuario no es + root (o porque el <code>httpd</code> que se est ejecutando + en ese momento ya est conectado a esos puertos). Si falla + por cualquier otra razn, entonces casi seguro que hay + algn error en alguno de los ficheros de configuracin y + debe corregir ese o esos errores antes de hacer un reinicio + graceful.</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="hup" id="hup">Reiniciar Apache</a></h2> + +<dl><dt>Seal: HUP</dt> +<dd><code>apachectl -k restart</code></dd> +</dl> + + <p>El envo de las seales <code>HUP</code> o + <code>restart</code> al proceso padre hace que los procesos hijo + terminen como si le envi ramos la seal + <code>TERM</code>, para eliminar el proceso padre. La diferencia + est en que estas seales vuelven a leer los archivos de + configuracin y vuelven a abrir los ficheros log. Se genera + un nuevo conjunto de hijos y se contina sirviendo + peticiones.</p> + + <p>Los usuarios del mdulo <code class="module"><a href="./mod/mod_status.html">mod_status</a></code> + notarn que las estadsticas del servidor se ponen a + cero cuando se enva la seal <code>HUP</code>.</p> + +<div class="note">Si su fichero de configuracin contiene errores, cuando +intente reiniciar, el proceso padre del servidor no se +reiniciar, sino que terminar con un error. Consulte +ms arriba cmo puede solucionar este problema.</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="race" id="race">Apndice: seales y race conditions</a></h2> + + <p>Con anterioridad a la versin de Apache 1.2b9 haba + varias <em>race conditions</em> implicadas en las seales + para parar y reiniciar procesos (una descripcin sencilla de + una race condition es: un problema relacionado con el momento en + que suceden las cosas, como si algo sucediera en momento en que no + debe, y entonces el resultado esperado no se corresponde con el + obtenido). Para aquellas arquitecturas que tienen el conjunto de + caractersticas "adecuadas", se han eliminado tantas race + conditions como ha sido posible. Pero hay que tener en cuenta que + todava existen race conditions en algunas arquitecturas.</p> + + <p>En las arquitecturas que usan un <code class="directive"><a href="./mod/mpm_common.html#scoreboardfile">ScoreBoardFile</a></code> en disco, existe la + posibilidad de que se corrompan los scoreboards. Esto puede hacer + que se produzca el error "bind: Address already in use" + (despus de usar<code>HUP</code>) o el error "long lost child + came home!" (despus de usar <code>USR1</code>). En el + primer caso se trata de un error irrecuperable, mientras que en el + segundo, solo ocurre que el servidor pierde un slot del + scoreboard. Por lo tanto, sera aconsejable usar reinicios + graceful, y solo hacer reinicios normales de forma + ocasional. Estos problemas son bastante complicados de solucionar, + pero afortunadamente casi ninguna arquitectura necesita un fichero + scoreboard. Consulte la documentacin de la directiva + <code class="directive"><a href="./mod/mpm_common.html#scoreboardfile">ScoreBoardFile</a></code> para ver + las arquitecturas que la usan.</p> + + <p>Todas las arquitecturas tienen una pequea race condition + en cada proceso hijo implicada en la segunda y subsiguientes + peticiones en una conexin HTTP persistente + (KeepAlive). Puede ser que el servidor termine despus de + leer la lnea de peticin pero antes de leer cualquiera + de las cebeceras de peticin. Hay una solucin que fue + descubierta demasiado tarde para la incluirla en versin + 1.2. En teoria esto no debe suponer ningn problema porque el + cliente KeepAlive ha de esperar que estas cosas pasen debido a los + retardos de red y a los timeouts que a veces dan los + servidores. En la practica, parece que no afecta a nada ms + -- en una sesin de pruebas, un servidor se reinici + veinte veces por segundo y los clientes pudieron navegar sin + problemas por el sitio web sin encontrar problemas ni para + descargar una sola imagen ni encontrar un solo enlace roto. </p> +</div></div> +<div class="bottomlang"> +<p><span>Idiomas disponibles: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" title="Espaol"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Franais"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Trke"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comentarios</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/stopping.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2019 The Apache Software Foundation.<br />Licencia bajo los trminos de la <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="menu"><a href="./mod/">Mdulos</a> | <a href="./mod/directives.html">Directivas</a> | <a href="http://wiki.apache.org/httpd/FAQ">Preguntas Frecuentes</a> | <a href="./glossary.html">Glosario</a> | <a href="./sitemap.html">Mapa del sitio web</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file diff --git a/docs/manual/stopping.html.fr.utf8 b/docs/manual/stopping.html.fr.utf8 new file mode 100644 index 0000000..e1c0bca --- /dev/null +++ b/docs/manual/stopping.html.fr.utf8 @@ -0,0 +1,305 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!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="fr" xml:lang="fr"><head> +<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Arrêt et redémarrage du serveur HTTP Apache - Serveur HTTP Apache Version 2.4</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 rel="stylesheet" type="text/css" href="./style/css/prettify.css" /> +<script src="./style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">Glossaire</a> | <a href="./sitemap.html">Plan du site</a></p> +<p class="apache">Serveur HTTP Apache Version 2.4</p> +<img alt="" src="./images/feather.png" /></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/">Serveur HTTP</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="./">Version 2.4</a></div><div id="page-content"><div id="preamble"><h1>Arrêt et redémarrage du serveur HTTP Apache</h1> +<div class="toplang"> +<p><span>Langues Disponibles: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="./fr/stopping.html" title="Français"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> + + <p>Ce document couvre l'arrêt et le redémarrage du + serveur HTTP Apache sur + les systèmes Unix et similaires. Les utilisateurs de Windows NT, 2000 + and XP doivent consulter + <a href="platform/windows.html#winsvc">Exécuter httpd en tant que + service</a> et les utilisateurs de Windows 9x et ME doivent consulter + <a href="platform/windows.html#wincons">Exécuter httpd comme une + application de type console</a> pour plus d'informations sur le contrôle + de httpd à partir de ces plateformes.</p> +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#introduction">Introduction</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#term">Arrêter immédiatement</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#graceful">Redémarrage en douceur</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#hup">Redémarrer immédiatement</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#gracefulstop">Arrêt en douceur</a></li> +</ul><h3>Voir aussi</h3><ul class="seealso"><li><code class="program"><a href="./programs/httpd.html">httpd</a></code></li><li><code class="program"><a href="./programs/apachectl.html">apachectl</a></code></li><li><a href="invoking.html">Démarrage</a></li><li><a href="#comments_section">Commentaires</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="introduction" id="introduction">Introduction</a></h2> + + <p>Afin d'arrêter ou redémarrer le serveur HTTP Apache, vous devez envoyer un signal aux + processus <code class="program"><a href="./programs/httpd.html">httpd</a></code> en cours d'exécution. Les signaux + peuvent être envoyés de deux manières. La + première méthode consiste à + utiliser la commande unix <code>kill</code> + pour envoyer directement des signaux aux processus. Vous pouvez remarquer + que plusieurs processus <code class="program"><a href="./programs/httpd.html">httpd</a></code> s'exécutent sur votre + système, mais il vous suffit d'envoyer les signaux au processus parent, + dont le PID est enregistré dans le fichier précisé par la directive + <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code>. Autrement dit, vous + n'aurez jamais besoin d'envoyer des signaux à aucun des + processus enfants, mais seulement au processus parent. Quatre types + de signaux peuvent être envoyés au processus parent : + <code><a href="#term">TERM</a></code>, + <code><a href="#graceful">USR1</a></code>, + <code><a href="#hup">HUP</a></code>, et + <code><a href="#gracefulstop">WINCH</a></code>, qui + seront décrit plus loin.</p> + + <p>Pour envoyer un signal au processus parent, vous devez entrer une commande + du style :</p> + +<div class="example"><p><code>kill -TERM `cat /usr/local/apache2/logs/httpd.pid`</code></p></div> + + <p>La seconde méthode permettant d'envoyer des signaux aux processus + <code class="program"><a href="./programs/httpd.html">httpd</a></code> + consiste à utiliser les options <code>stop</code>, + <code>restart</code>, <code>graceful</code> et + <code>graceful-stop</code> du commutateur <code>-k</code> de la ligne + de commande comme décrit ci-dessous. Ce sont des arguments du binaire + <code class="program"><a href="./programs/httpd.html">httpd</a></code>, mais il est recommandé de les utiliser + avec le script de contrôle <code class="program"><a href="./programs/apachectl.html">apachectl</a></code>, qui se + chargera de les passer à <code class="program"><a href="./programs/httpd.html">httpd</a></code>.</p> + + <p>Après avoir envoyé un signal à <code class="program"><a href="./programs/httpd.html">httpd</a></code>, vous pouvez + suivre le cours de son action en entrant :</p> + +<div class="example"><p><code>tail -f /usr/local/apache2/logs/error_log</code></p></div> + + <p>Adaptez ces exemples en fonction de la définition de vos directives + <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code> et + <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</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="term" id="term">Arrêter immédiatement</a></h2> + +<dl><dt>Signal: TERM</dt> +<dd><code>apachectl -k stop</code></dd> +</dl> + + <p>A la réception du signal <code>TERM</code> ou <code>stop</code>, + le processus parent tente immédiatement + de tuer tous ses processus enfants. Cela peut durer plusieurs secondes. + Après cela, le processus parent lui-même se termine. Toutes les requêtes + en cours sont terminées, et plus aucune autre n'est traitée.</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="graceful" id="graceful">Redémarrage en douceur</a></h2> + +<dl><dt>Signal: USR1</dt> +<dd><code>apachectl -k graceful</code></dd> +</dl> + + <p>A la réception du signal <code>USR1</code> ou + <code>graceful</code>, le + processus parent envoie aux processus enfants + <em>l'ordre</em> de se terminer une fois leur requête courante + traitée (ou de se terminer immédiatement s'ils n'ont plus rien à traiter). + Le processus parent relit ses fichiers de configuration et + réouvre ses fichiers de log. Chaque fois qu'un enfant s'éteint, le + processus parent le remplace par un processus + enfant de la nouvelle <em>génération</em> de la + configuration, et celui-ci commence immédiatement à traiter les + nouvelles requêtes.</p> + + <p>Ce code est conçu pour toujours respecter la directive de contrôle + de processus des modules MPMs, afin que les nombres de processus et de + threads + disponibles pour traiter les demandes des clients soient maintenus à + des valeurs appropriées tout au long du processus de démarrage. + En outre, il respecte la directive + <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> de la manière + suivante : si après une seconde au moins <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> nouveaux processus + enfants n'ont pas été créés, un nombre suffisant de processus + supplémentaires est créé pour combler le manque. Ainsi le code + tente de maintenir à la fois le nombre approprié de processus enfants + en fonction de la charge du serveur, et le nombre de processus défini par la + directive <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code>.</p> + + <p>Les utilisateurs du module <code class="module"><a href="./mod/mod_status.html">mod_status</a></code> + noteront que les statistiques du serveur ne sont <strong>pas</strong> + remises à zéro quand un signal <code>USR1</code> est envoyé. Le code + a été conçu à la fois pour minimiser la durée durant laquelle le + serveur ne peut pas traiter de nouvelles requêtes (elle sont mises en + file d'attente par le système d'exploitation, et ne sont ainsi jamais + perdues) et pour respecter vos paramètres de personnalisation. + Pour y parvenir, il doit conserver le + <em>tableau</em> utilisé pour garder la trace de tous les processus + enfants au cours des différentes générations.</p> + + <p>Dans son état des processus, + le module status utilise aussi un caractère <code>G</code> afin d'indiquer + quels processus enfants ont encore des traitements de requêtes en cours + débutés avant que l'ordre graceful restart ne soit donné.</p> + + <p>Pour l'instant, il est impossible pour un script de rotation + des logs utilisant + <code>USR1</code> de savoir de manière certaine si tous les processus + enfants inscrivant des traces de pré-redémarrage sont terminés. + Nous vous suggérons d'attendre un délai suffisant après l'envoi du + signal <code>USR1</code> + avant de faire quoi que ce soit avec les anciens logs. Par exemple, + si la plupart de vos traitements durent moins de 10 minutes pour des + utilisateurs empruntant des liaisons à faible bande passante, alors vous + devriez attendre 15 minutes avant de faire quoi que ce soit + avec les anciens logs.</p> + + <div class="note"> + <p>Lorsque vous initiez un redémarrage, une vérification de + la syntaxe est tout d'abord effectuée, afin de s'assurer qu'il n'y a + pas d'erreurs dans les fichiers de configuration. Si votre fichier de + configuration comporte des erreurs de syntaxe, vous recevrez un message + d'erreur les concernant, et le serveur refusera de redémarrer. Ceci + permet d'éviter la situation où un serveur a + été arrêté et ne peut plus redémarrer, + et où vous vous retrouvez avec un serveur hors-service.</p> + + <p>Ceci ne garantit pas encore que le serveur va redémarrer + correctement. Pour vérifier la sémantique des fichiers de configuration + en plus de leur syntaxe, vous pouvez essayer de démarrer + <code class="program"><a href="./programs/httpd.html">httpd</a></code> sous un utilisateur non root. + S'il n'y a pas d'erreur, il tentera d'ouvrir ses sockets et ses fichiers + de log et échouera car il n'a pas les privilèges root (ou parce que + l'instance actuelle de + <code class="program"><a href="./programs/httpd.html">httpd</a></code> est déjà associée à ces ports). S'il échoue + pour toute autre raison, il y a probablement une erreur dans le + fichier de configuration et celle-ci doit être corrigée avant de lancer + le redémarrage en douceur.</p></div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="hup" id="hup">Redémarrer immédiatement</a></h2> + +<dl><dt>Signal: HUP</dt> +<dd><code>apachectl -k restart</code></dd> +</dl> + + <p>A la réception du signal <code>HUP</code> ou + <code>restart</code>, le + processus parent tue ses processus enfants comme pour le signal + <code>TERM</code>, mais le processus parent ne se termine pas. + Il relit ses fichiers de configuration, et réouvre ses fichiers de log. + Puis il donne naissance à un nouveau jeu de processus enfants + et continue de traiter les requêtes.</p> + + <p>Les utilisateurs du module <code class="module"><a href="./mod/mod_status.html">mod_status</a></code> + noteront que les statistiques du serveur sont remises à zéro quand un + signal <code>HUP</code> est envoyé.</p> + +<div class="note">Comme dans le cas d'un redémarrage "graceful", une +vérification de la syntaxe est effectuée avant que le +redémarrage ne soit tenté. Si votre fichier de configuration comporte +des erreurs de syntaxe, le redémarrage ne sera pas effectué, et +vous recevrez un message concernant ces erreurs.</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="gracefulstop" id="gracefulstop">Arrêt en douceur</a></h2> + +<dl><dt>Signal : WINCH</dt> +<dd><code>apachectl -k graceful-stop</code></dd> +</dl> + + <p>A la réception du signal <code>WINCH</code> ou + <code>graceful-stop</code>, le + processus parent <em>ordonne</em> à ses processus enfants + de s'arrêter après le traitement de leur requête en cours + (ou de s'arrêter immédiatement s'ils n'ont plus de requête à traiter). + Le processus parent va alors supprimer son fichier + <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> et cesser l'écoute + de tous ses ports. Le processus parent va continuer à s'exécuter, + et va surveiller les processus enfants + qui ont encore des requêtes à traiter. Lorsque tous les processus enfants + ont terminé leurs traitements et se sont arrêtés ou lorsque le délai + spécifié par la directive <code class="directive"><a href="./mod/mpm_common.html#gracefulshutdowntimeout">GracefulShutdownTimeout</a></code> a été atteint, + le processus parent s'arrêtera à son tour. Si ce délai est atteint, + tout processus enfant encore en cours d'exécution se verra envoyer + le signal <code>TERM</code> + afin de le forcer à s'arrêter.</p> + + <p>L'envoi du signal <code>TERM</code> va arrêter immédiatement + les processus parent et enfants en état "graceful". Cependant, + comme le fichier <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> + aura été supprimé, vous ne pourrez pas utiliser + <code>apachectl</code> ou <code>httpd</code> pour envoyer ce signal.</p> + + <div class="note"><p>Le signal <code>graceful-stop</code> vous permet d'exécuter + simultanément plusieurs instances de <code class="program"><a href="./programs/httpd.html">httpd</a></code> + avec des configurations identiques. Ceci s'avère une fonctionnalité + puissante quand vous effectuez des mises à jour "en douceur" + de httpd ; cependant, cela peut aussi causer des blocages fatals et des + situations de compétition (race conditions) + avec certaines configurations.</p> + + <p>On a pris soin de s'assurer que les fichiers sur disque + comme les fichiers verrou (<code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code>) et les fichiers socket Unix + (<code class="directive"><a href="./mod/mod_cgid.html#scriptsock">ScriptSock</a></code>) contiennent le PID + du serveur, et coexistent sans problème. Cependant, si une directive de + configuration, un module tiers ou une CGI résidente utilise un autre + verrou ou fichier d'état sur disque, il faut prendre soin de s'assurer + que chaque instance de <code class="program"><a href="./programs/httpd.html">httpd</a></code> qui s'exécute + n'écrase pas les fichiers des autres instances.</p> + + <p>Vous devez aussi prendre garde aux autres situations de compétition, + comme l'enregistrement des logs avec un transfert de ceux-ci + via un pipe vers le programme <code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code>. Plusieurs instances + du programme <code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code> qui tentent d'effectuer + une rotation des mêmes fichiers de log en même temps peuvent détruire + mutuellement leurs propres fichiers de log.</p></div> +</div></div> +<div class="bottomlang"> +<p><span>Langues Disponibles: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="./fr/stopping.html" title="Français"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Commentaires</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/stopping.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2019 The Apache Software Foundation.<br />Autorisé sous <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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">Glossaire</a> | <a href="./sitemap.html">Plan du site</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file diff --git a/docs/manual/stopping.html.ja.utf8 b/docs/manual/stopping.html.ja.utf8 new file mode 100644 index 0000000..d307b2f --- /dev/null +++ b/docs/manual/stopping.html.ja.utf8 @@ -0,0 +1,279 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!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="ja" xml:lang="ja"><head> +<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Apache HTTP Server の停止と再起動 - Apache HTTP サーバ バージョン 2.4</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 rel="stylesheet" type="text/css" href="./style/css/prettify.css" /> +<script src="./style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">用語</a> | <a href="./sitemap.html">サイトマップ</a></p> +<p class="apache">Apache HTTP サーバ バージョン 2.4</p> +<img alt="" src="./images/feather.png" /></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 サーバ</a> > <a href="http://httpd.apache.org/docs/">ドキュメンテーション</a> > <a href="./">バージョン 2.4</a></div><div id="page-content"><div id="preamble"><h1>Apache HTTP Server の停止と再起動</h1> +<div class="toplang"> +<p><span>翻訳済み言語: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | +<a href="./ja/stopping.html" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> + + <p>この文書では Unix に類似したシステムでの + Apache HTTP Serverの停止と再起動について扱っています。 + Windows NT, 2000, XP ユーザは<a href="platform/windows.html#winsvc">サービスとして + httpd を実行する</a>で、Windows 9x, MEユーザは<a href="platform/windows.html#wincons">コンソールアプリケーションとして + httpd を実行する</a>で、 + これらのプラットホームでの使用方法をご覧下さい。</p> +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#introduction">イントロダクション</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#term">急な停止</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#graceful">緩やかな再起動</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#hup">急な再起動</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#gracefulstop">緩やかな停止</a></li> +</ul><h3>参照</h3><ul class="seealso"><li><code class="program"><a href="./programs/httpd.html">httpd</a></code></li><li><code class="program"><a href="./programs/apachectl.html">apachectl</a></code></li><li><a href="invoking.html">Starting</a></li><li><a href="#comments_section">コメント</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="introduction" id="introduction">イントロダクション</a></h2> + + <p>Apache HTTP Server を停止したり再起動したりするためには、実行されている + <code class="program"><a href="./programs/httpd.html">httpd</a></code> プロセスにシグナルを送る必要があります。 + シグナルを送るには二つの方法があります。 + 一つ目はプロセスに直接シグナルを送る unix の <code>kill</code> + コマンドを使用する方法です。 + システムを見ればたくさんの <code class="program"><a href="./programs/httpd.html">httpd</a></code> が + 実行されているのに気が付くでしょうが、シグナルを送るのは + 親プロセスだけで、それ以外の個々のプロセスには + シグナルを送らないで下さい。その親プロセスの pid は + <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> + に書かれています。これはつまり、親以外のプロセスに + シグナルを送る必要すらない、ということです。 + 親プロセスに送ることができる 4 種類のシグナルがあります: + <code><a href="#term">TERM</a></code>, + <code><a href="#hup">HUP</a></code>, + <code><a href="#graceful">USR1</a></code>, + <code><a href="#gracefulstop">WINCH</a></code> + です。これらの説明については続きをご覧下さい。</p> + + <p>親プロセスにシグナルを送るには、 + 次のようなコマンドを発行して下さい:</p> + +<div class="example"><p><code>kill -TERM `cat /usr/local/apache2/logs/httpd.pid`</code></p></div> + + <p><code class="program"><a href="./programs/httpd.html">httpd</a></code> プロセスにシグナルを送る 2 番目の方法は + <code>-k</code> というコマンドライン引数を使用することです。 + 下で説明されているように、<code>stop</code>, <code>restart</code>, + <code>graceful</code>, <code>graceful-stop</code> を指定できます。 + これらは <code class="program"><a href="./programs/httpd.html">httpd</a></code> の引数ですが、 + 制御用のスクリプト <code class="program"><a href="./programs/apachectl.html">apachectl</a></code> はそれらの引数をそのまま + <code class="program"><a href="./programs/httpd.html">httpd</a></code> に渡します。</p> + + <p><code class="program"><a href="./programs/httpd.html">httpd</a></code> にシグナルを送った後、 + 実行状況を次のコマンドで読むことができます:</p> + +<div class="example"><p><code>tail -f /usr/local/apache2/logs/error_log</code></p></div> + <p>ここに挙げた例は、各自の + <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code> + と + <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</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="term" id="term">急な停止</a></h2> + +<dl><dt>シグナル: TERM</dt> +<dd><code>apachectl -k stop</code></dd> +</dl> + + <p><code>TERM</code> あるいは <code>stop</code> + シグナルを親プロセスに送ると、即座に子プロセス全てを kill しようとします。 + 子プロセスを完全に kill し終わるまでに数秒かかるかもしれません。 + その後、親プロセス自身が終了します。 + 処理中のリクエストは全て停止され、もはやリクエストに対する + 応答はされません。</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="graceful" id="graceful">緩やかな再起動</a></h2> + +<dl><dt>シグナル: USR1</dt> +<dd><code>apachectl -k graceful</code></dd> +</dl> + + <p>親プロセスは <code>USR1</code> あるいは <code>graceful</code> + シグナルを受け取ると、子プロセスに現在のリクエストの処理の後に終了する + (あるいは何もしていなければすぐに終了する) + ように<em>助言</em>します。 + 親プロセスは設定ファイルを再読込して、ログファイルを開き直します。 + 子プロセスが徐々になくなるに従って、 + 新しい<em>世代</em>の設定による子プロセスに置き換えていきます。 + そして、これらが新たなリクエストに即座に応答し始めます。</p> + + <p>このコードは常に + MPM のプロセス制御ディレクティブの設定を重視しますので、 + クライアントのリクエストを扱うプロセスとスレッドの数を再起動の処理中も + 適切な値に維持されます。。また、次のようにして + <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> + を守ります: + 少なくとも 1 秒後に <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> 個の新しい子プロセスが + 生成されていなければ、その数になるように適宜プロセスを生成します。 + この挙動は現在の負荷に対して適切な子プロセスの数と + <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> パラメータでの + 希望の数の両方を維持しようとしています。</p> + + <p><code class="module"><a href="./mod/mod_status.html">mod_status</a></code> を + 使用している場合は、<code>USR1</code> シグナルが送られた際に + サーバ統計がゼロに<strong>設定されない</strong>ことに + 注意してください。 + サーバが新しいリクエストに応答不能な時間を最小にするように + (リクエストは OS によってキューに追加されるので絶対に紛失はしません)、 + また同時に、希望のチューニングパラメータを守るように + コードは書かれています。 + このようにするために、世代をまたがった全子プロセスの追跡に使われている + <em>スコアボード</em>を維持しなければなりません。</p> + + <p>status モジュールは、緩やかな再起動以前から開始して + リクエストに応答し続けている子プロセスを特定するために、 + <code>G</code> を使うこともします。</p> + + <p>現在、<code>USR1</code> を使うログ移動スクリプトでは、 + 再起動前の子プロセスがログを書き終わったことを確証する方法が + ありません。古いログに対して何かする前に、 + <code>USR1</code> シグナルを送った後いくらか適当な時間待つことを + 提案します。例えば、帯域の狭い通信路のユーザのリクエストのほとんどが 10 + 分以下で完了しているということが分かっていれば、 + 古いログに何かする前に 15 分待つということです。</p> + + <div class="note"><p>再起動が発行されると設定ファイルの構文チェックがまず走り、 + 設定ファイルに (構文上の) 誤りがないかチェックされます。 + 誤りがあった場合エラーメッセージでその旨が示され、サーバは再起動されません。 + こうすることでサーバが終了しているけれども再起動できないという状況を + 防ぎ、サーバが機能不全な状態になるのを防いでいます。</p> + + <p>ただしこれでもサーバが正しく再起動することは保証されません。 + 設定ファイルの意味的な内容を構文と同様に検証したい場合は、 + 非 root ユーザで <code class="program"><a href="./programs/httpd.html">httpd</a></code> を起動しようとすればわかります。 + もしエラーがなければ、ソケットやログを開こうとして + root でないため + (もしくは実行中の <code class="program"><a href="./programs/httpd.html">httpd</a></code> + が既に必要なポートにバインドしているため) + に失敗するでしょう。 + これ以外の理由で起動に失敗したのであれば、 + それは設定ファイルのエラーで、 + 緩やかな再起動を行う前にその誤りを修正しなければなりません。</p> + </div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="hup" id="hup">急な再起動</a></h2> + +<dl><dt>シグナル: HUP</dt> +<dd><code>apachectl -k restart</code></dd> +</dl> + + <p><code>HUP</code> あるいは <code>restart</code> シグナルを親プロセスに送ると、 + <code>TERM</code> と同様に子プロセスを kill しますが、 + 親プロセスは終了しません。 + 設定ファイルを再読込して、ログファイル全てを開き直します。 + その後、新しい子プロセスを起動して応答を続けます。</p> + + <p><code class="module"><a href="./mod/mod_status.html">mod_status</a></code> + を使っている場合は、<code>HUP</code> が送られた場合に + サーバ統計がゼロに設定されることに注意してください。</p> + + <div class="note">graceful 再起動時は、再起動前に構文チェックが行われます。 + もし構文エラーがあればその旨が示され、再起動は行われません。</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="gracefulstop" id="gracefulstop">緩やかな停止</a></h2> + +<dl><dt>Signal: WINCH</dt> +<dd><code>apachectl -k graceful-stop</code></dd> +</dl> + + <p><code>WINCH</code> や <code>graceful-stop</code> シグナルを受け取ると、 + 親プロセスは子プロセスに現在処理中のリクエストの後に終了する + (あるいは処理中のものが何もなければ直ちに終了する) + ように<em>アドバイス</em>します。 + その後親プロセスは <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> + を削除し、ポートでの Listen を全て停止します。 + 親プロセスはどの子プロセスがリクエスト処理中かを監視し続けています。 + 全ての子プロセスが終了するか + <code class="directive"><a href="./mod/mpm_common.html#gracefulshutdowntimeout">GracefulShutdownTimeout</a></code> + で設定した時間が過ぎると、親プロセスも終了します。 + タイムアウトに達した場合、残りの子プロセスには <code>TERM</code> + シグナルが送信され強制的に終了されます。</p> + + <p>"graceful" 状態の場合 <code>TERM</code> シグナルを受け取ると、 + 親プロセスも子プロセスもすぐに終了します。しかしながら + <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> + が削除されてしまっているので、<code>apachectl</code> + や <code>httpd</code> にこのシグナルを送ることはできません。</p> + + <div class="note"><p><code>graceful-stop</code> を使うとまったく同一に設定された + 複数の <code class="program"><a href="./programs/httpd.html">httpd</a></code> を同時に実行することができます。 + httpd を緩やかにアップグレードするのにはとても便利ですが、 + 設定ファイルによってはデッドロックやレースコンディションを + 引き起こすこともあります。</p> + + <p>ディスク上のファイルを使うもの、たとえばロックファイル + (<code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code>) や Unix ソケットファイル + (<code class="directive"><a href="./mod/mod_cgid.html#scriptsock">ScriptSock</a></code>) + などはサーバの PID を含めて管理されていて、 + 共存できるよう注意が払われています。 + しかしその他設定ディレクティブやサードパーティ製のモジュール、 + CGI ユーティリティのパーシステント層などで + ディスク上にロックファイルや状態管理ファイルを + 使っている場合は、実行されている複数の <code class="program"><a href="./programs/httpd.html">httpd</a></code> + が互いに衝突しないように気をつけなければなりません。</p> + + <p><code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code> 形式のパイプを使ったログといった、 + その他潜在的なレースコンディションについても注意しなければなりません。 + 複数の <code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code> が同じファイルを同時に + rotate しようとすると、互いにログファイルを破壊してしまいます。</p> + </div> +</div></div> +<div class="bottomlang"> +<p><span>翻訳済み言語: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | +<a href="./ja/stopping.html" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">コメント</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/stopping.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2019 The Apache Software Foundation.<br />この文書は <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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">用語</a> | <a href="./sitemap.html">サイトマップ</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file diff --git a/docs/manual/stopping.html.ko.euc-kr b/docs/manual/stopping.html.ko.euc-kr new file mode 100644 index 0000000..7f083c9 --- /dev/null +++ b/docs/manual/stopping.html.ko.euc-kr @@ -0,0 +1,235 @@ +<?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> +<meta content="text/html; charset=EUC-KR" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>ߴܰ - Apache HTTP Server Version 2.4</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 rel="stylesheet" type="text/css" href="./style/css/prettify.css" /> +<script src="./style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html"></a> | <a href="./sitemap.html">Ʈ</a></p> +<p class="apache">Apache HTTP Server Version 2.4</p> +<img alt="" src="./images/feather.png" /></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.4</a></div><div id="page-content"><div id="preamble"><h1>ߴܰ </h1> +<div class="toplang"> +<p><span> : </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div> +<div class="outofdate"> ֽ ƴմϴ. + ֱٿ ϼ.</div> + + <p> н ýۿ ġ ߴϰ ϴ + ִ. NT, 2000, XP ڴ <a href="platform/windows.html#winsvc"> ġ + ϱ</a>, 9x ME ڴ <a href="platform/windows.html#wincons">ݼ α + ġ ϱ</a> ÷ ġ ۹ ִ.</p> +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#introduction">Ұ</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#term"> ߴ</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#graceful"> </a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#hup"> </a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#race">η: ñ׳ΰ ̽ </a></li> +</ul><h3></h3><ul class="seealso"><li><a href="programs/httpd.html">httpd</a></li><li><a href="programs/apachectl.html">apachectl</a></li><li><a href="#comments_section">Comments</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="introduction" id="introduction">Ұ</a></h2> + + <p>ġ ߴϰ Ϸ ϰ ִ + <code>httpd</code> μ ñ׳ Ѵ. ñ׳ + ΰ. ϳ н <code>kill</code> + ɾ Ͽ μ ñ׳ ̴. + ýۿ <code>httpd</code> , <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> pid ϵ θܿ + ٸ μ ñ׳(signal) ȵȴ. , θ̿ܿ + ٸ μ ñ׳ ʿ䰡 ٴ ̴. θ + ִ ñ׳ , <code><a href="#term">TERM</a></code>, <code><a href="#hup">HUP</a></code>, <code><a href="#graceful">USR1</a></code>̴.</p> + + <p> θ ñ׳ :</p> + +<div class="example"><p><code>kill -TERM `cat /usr/local/apache2/logs/httpd.pid`</code></p></div> + + <p><code>httpd</code> μ ñ׳ ٸ + ɼ <code>-k</code> ϴ ̴. Ʒ + <code>stop</code>, <code>restart</code>, <code>graceful</code> + <a href="programs/httpd.html">httpd</a> ƱԸƮ̴. + ƱԸƮ <code>httpd</code> ϴ, <a href="programs/apachectl.html">apachectl</a> ũƮ + ϱ Ѵ.</p> + + <p><code>httpd</code> ñ׳ , ɾ + Ȳ ִ:</p> + +<div class="example"><p><code>tail -f /usr/local/apache2/logs/error_log</code></p></div> + + <p> <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code> <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</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="term" id="term"> ߴ</a></h2> + +<dl><dt>ñ׳: TERM</dt> +<dd><code>apachectl -k stop</code></dd> +</dl> + + <p><code>TERM</code>̳ <code>stop</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="graceful" id="graceful"> </a></h2> + +<dl><dt>ñ׳: USR1</dt> +<dd><code>apachectl -k graceful</code></dd> +</dl> + + <p><code>USR1</code>̳ <code>graceful</code> ñ׳ + θ θ μ ڽĵ鿡 û + ó ϶ (Ȥ ƹ͵ ó ʴٸ + ϶) <em>Ѵ</em>. θ + ٽа αϵ ٽ . ڽ θ + ڽĴ ο <em></em> ڽ + Ͽ û óϰ Ѵ.</p> + + <div class="note"> (graceful restart) <code>USR1</code> + ÷ (<code>WINCH</code> ) + ٸ ñ׳ ִ. <code>apachectl graceful</code> + ÷ ˸ ñ׳ .</div> + + <p> MPM μ þ + Ͽ, ۵ Ŭ̾Ʈ ϴ μ 尡 + ϵ Ǿ. Դٰ <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code>, + ּ StartServersŭ ο ڽ ȸ ڽ + StartServers ǵ . , α + Ͽ ˸ ڽ ϸ, + <code class="directive">StartServers</code> Ķͷ + 븦 Ѵ.</p> + + <p><code class="module"><a href="./mod/mod_status.html">mod_status</a></code> ڴ <code>USR1</code> + 谡 0 <strong></strong> + ̴. ο û (ü ̵ ť Ƽ + 쿡 Ҿ ʴ´) ó ϴ ð + ּȭϰ Ʃ Ķ ϵ . + ̸ 밣 ڽ ϴ <em>scoreboard</em> + Ѵ.</p> + + <p>status Ͽ + û óϰ ִ ڽ <code>G</code> ˷ش.</p> + + <p>δ <code>USR1</code> ϴ αȯ ũƮ + ڽ αۼ ƴ ִ + . 츮 <code>USR1</code> ñ׳ + ð α ٷ絵 Ѵ. + 뿪 κ ġµ 10 + Ȱɸٸ, α ٷ 15 ٸ.</p> + + <div class="note">Ͽ ִٸ ۽ θ + ʰ Ѵ. , Ҷ + ڽ ǵ д. (ڽĵ ڽ û + óϰ "ݰ Ѵ".) ̴ Ҷ + ȴ. ڽ ٸ Ʈ Ѵ. + <code>-t</code> ɼ(<a href="programs/httpd.html">httpd</a> ) + ˻ ִ. ̷ ˻絵 ùٷ + Ѵ. ƴ ǹ̸ + ˻Ϸ root ƴ ڷ <code>httpd</code> غ ִ. + root ƴϱ (ƴϸ Ʈ ϴ + <code>httpd</code> DZ) ٸ ϰ + α õϴ ̴. ٸ + Ѵٸ Ƹ Ͽ ̴. + ϱ ľѴ.</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="hup" id="hup"> </a></h2> + +<dl><dt>ñ׳: HUP</dt> +<dd><code>apachectl -k restart</code></dd> +</dl> + + <p><code>HUP</code>̳ <code>restart</code> ñ׳ + θ <code>TERM</code> ڽ + θ ʴ´. θ ٽа + α ٽ . ο ڽĵ + Ѵ.</p> + + <p><code class="module"><a href="./mod/mod_status.html">mod_status</a></code> ڴ <code>HUP</code> + 谡 0 ִ.</p> + +<div class="note">Ͽ ִٸ ص θ +ʰ ̴. ̸ ϴ ϶.</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="race" id="race">η: ñ׳ΰ ̽ </a></h2> + + <p>Apache 1.2b9 ۰ ñ׳ο + <em>̽ (race condition)</em> ־. (̽ + ڸ, ߸ȶ Ͼ + Ѵ ʴ ð ΰ .) "ùٸ" + ִ ŰĿ 츮 ̷ ִ ذߴ. + ŰĿ ̽ + ϶.</p> + + <p><code class="directive"><a href="./mod/mpm_common.html#scoreboardfile">ScoreBoardFile</a></code> + ũ ϴ ŰĴ scoreboard Ʈ ɼ + ִ. (<code>HUP</code>) "bind: Address already in use" + Ȥ (<code>USR1</code> ) "long lost child came home!" + ִ. ڴ ɰ ̰, ڴ + scoreboard slot Ұ . ̰ + ϱ õѴ. ذϱ ſ + . κ ŰĴ scoreboard + ʴ´. ϴ ŰĶ <code class="directive"><a href="./mod/mpm_common.html#scoreboardfile">ScoreBoardFile</a></code> ϶.</p> + + <p> ŰĿ ӵǴ HTTP (KeepAlive) + ι° û óϴ ڽĿ ణ ̽ + ִ. ڽ û û б + ִ. ʹ ʰ ߰Ͽ 1.2 Ŀ + Ǿ. Ʈ ̳ ðѶ KeepAlive + Ŭ̾Ʈ ̷ 츦 ؾϱ ̷л + ȵȴ. ˻ϱ ʿ 20 ϴ + Ŭ̾Ʈ ̳ Ʈ + о̱ ʴ´ٸ ȵȴ.</p> +</div></div> +<div class="bottomlang"> +<p><span> : </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" title="Korean"> ko </a> | +<a href="./tr/stopping.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/stopping.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2019 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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html"></a> | <a href="./sitemap.html">Ʈ</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file diff --git a/docs/manual/stopping.html.tr.utf8 b/docs/manual/stopping.html.tr.utf8 new file mode 100644 index 0000000..048505c --- /dev/null +++ b/docs/manual/stopping.html.tr.utf8 @@ -0,0 +1,273 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!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="tr" xml:lang="tr"><head> +<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /> +<!-- + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + This file is generated from xml source: DO NOT EDIT + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + --> +<title>Apache HTTP Sunucusunun Durdurulması ve Yeniden Başlatılması - Apache HTTP Sunucusu Sürüm 2.4</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 rel="stylesheet" type="text/css" href="./style/css/prettify.css" /> +<script src="./style/scripts/prettify.min.js" type="text/javascript"> +</script> + +<link href="./images/favicon.ico" rel="shortcut icon" /></head> +<body id="manual-page"><div id="page-header"> +<p class="menu"><a href="./mod/">Modüller</a> | <a href="./mod/directives.html">Yönergeler</a> | <a href="http://wiki.apache.org/httpd/FAQ">SSS</a> | <a href="./glossary.html">Terimler</a> | <a href="./sitemap.html">Site Haritası</a></p> +<p class="apache">Apache HTTP Sunucusu Sürüm 2.4</p> +<img alt="" src="./images/feather.png" /></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 Sunucusu</a> > <a href="http://httpd.apache.org/docs/">Belgeleme</a> > <a href="./">Sürüm 2.4</a></div><div id="page-content"><div id="preamble"><h1>Apache HTTP Sunucusunun Durdurulması ve Yeniden Başlatılması</h1> +<div class="toplang"> +<p><span>Mevcut Diller: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" title="Türkçe"> tr </a></p> +</div> + + <p>Bu belge Apache HTTP Sunucusunun Unix benzeri sistemlerde durdurulması + ve yeniden başlatılması konularını kapsar. Windows NT, 2000 ve XP + kullanıcıları Apache HTTPd’yi bu platformlarda nasıl denetimlerine + alacaklarını öğrenmek için <a href="platform/windows.html#winsvc">httpd’nin Bir Hizmet Olarak Çalıştırılması</a> sayfasına, Windows 9x ve + ME kullanıcıları ise <a href="platform/windows.html#wincons">httpd’nin + Bir Konsol Uygulaması Olarak Çalıştırılması</a> sayfasına + bakabilirler.</p> +</div> +<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#introduction">Giriş</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#term">Hemen Durdur</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#graceful">Nazikçe Yeniden Başlat</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#hup">Hemen Yeniden Başlat</a></li> +<li><img alt="" src="./images/down.gif" /> <a href="#gracefulstop">Nazikçe Durdur</a></li> +</ul><h3>Ayrıca bakınız:</h3><ul class="seealso"><li><code class="program"><a href="./programs/httpd.html">httpd</a></code></li><li><code class="program"><a href="./programs/apachectl.html">apachectl</a></code></li><li><a href="invoking.html">Başlatma</a></li><li><a href="#comments_section">Yorum</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="introduction" id="introduction">Giriş</a></h2> + + <p>Apache HTTP Sunucusunu durdurmak ve yeniden başlatmak için çalışan + <code class="program"><a href="./programs/httpd.html">httpd</a></code> süreçlerine bir sinyal göndermeniz gerekir. + Sinyal göndermek için iki yol vardır. İlki, süreçlere doğrudan sinyal + göndermek için unix <code>kill</code> komutunun kullanımıdır. Bu + suretle, sisteminizde çalışmakta olan bir çok <code class="program"><a href="./programs/httpd.html">httpd</a></code> + sürecini uyarabilirsiniz ama süreç kimliği <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> yönergesi ile belirtilen dosyada + tutulan ana süreç dışında hiçbirine sinyal göndermemelisiniz. Başka + bir deyişle, ana süreç haricinde hiçbir sürece sinyal göndermeye normal + olarak ihtiyacınız olmaması gerekir. Ana sürece gönderebileceğiniz + dört çeşit sinyal vardır: + <code><a href="#term">TERM</a></code>, + <code><a href="#graceful">USR1</a></code>, + <code><a href="#hup">HUP</a></code> ve + <code><a href="#gracefulstop">WINCH</a></code>. Bunlar yeri geldikçe + açıklanacaktır.</p> + + <p>Ana sürece <code>kill</code> ile sinyal göndermek için şöyle bir + komut verebilirsiniz:</p> + + <div class="example"><p><code>kill -TERM `cat /usr/local/apache2/logs/httpd.pid`</code></p></div> + + <p><code class="program"><a href="./programs/httpd.html">httpd</a></code> süreçlerine sinyal göndermenin ikinci yolu + <code>-k</code> komut satırı seçeneğini şu değerlerden biri ile + kullanmaktır: <code>stop</code>, <code>restart</code>, + <code>graceful</code> ve <code>graceful-stop</code>. Bunlar aşağıda + açıklanacaktır. <code>-k</code> komut satırı seçeneği + <code class="program"><a href="./programs/httpd.html">httpd</a></code>’ye ait olsa da ana sürece bu sinyalleri + göndermek için <code class="program"><a href="./programs/apachectl.html">apachectl</a></code> betiğini kullanmanızı + öneririz. <code class="program"><a href="./programs/apachectl.html">apachectl</a></code>, komut satırı seçeneklerini + <code class="program"><a href="./programs/httpd.html">httpd</a></code>’ye aktaracaktır.</p> + + <p><code class="program"><a href="./programs/httpd.html">httpd</a></code>’ye sinyal gönderdikten sonra olup biteni şu + komutla izleyebilirsiniz:</p> + + <div class="example"><p><code>tail -f /usr/local/apache2/logs/error_log</code></p></div> + + <p>Bu örnekleri, kendi <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code> ve + <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> yönergelerinizdeki + ayarlara uygun olarak değiştirdikten sonra kullanınız.</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="term" id="term">Hemen Durdur</a></h2> + + <dl><dt>Sinyal: TERM</dt> + <dd><code>apachectl -k stop</code></dd> + </dl> + + <p>Ana sürece <code>TERM</code> veya <code>stop</code> sinyali + göndererek tüm çocukların bir an önce öldürülmeye çalışılmasını sağlamış + olursunuz. Tüm çocukların öldürülmesi bir kaç saniye sürebilir. Son + olarak ana süreç çıkacaktır. Yanıtlanmakta olan istekler hemen + sonlandırılacak ve artık isteklere yanıt verilmeyecektir.</p> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="graceful" id="graceful">Nazikçe Yeniden Başlat</a></h2> + + <dl><dt>Sinyal: USR1</dt> + <dd><code>apachectl -k graceful</code></dd> + </dl> + + <p>Ana sürece <code>USR1</code> veya <code>graceful</code> sinyalinin + gönderilmesi, çocuklara ellerindeki mevcut işleri bitirdikten sonra + (veya sundukları bir şey yoksa hemen) çıkmalarının <em>önerilmesi</em> + demektir. Ana süreç kendi yapılandırma dosyalarını yeniden okur ve + kendi günlük dosyalarını yeniden açar. Ana sürecin öldürdüğü her sürecin + yerine yeni yapılandırma <em>kuşağından</em> bir süreç başlatır ve hemen + yeni isteklere hizmet sunulmaya başlanır.</p> + + <p>Bu kod MPM’lerin süreçleri denetleyen yönergelerine daima uyacak + şekilde tasarlanmıştır. Bu suretle, istemcilere hizmet sunacak çocuk + süreçler ve evreler, yeniden başlatma işleminde de uygun sayıda + sağlanmış olur. Bununla birlikte, <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> yönergesinde şöyle + davranılır: İlk saniye içinde en azından <code class="directive"><a href="./mod/mpm_common.html#startservers">StartServers</a></code> sayıda yeni çocuk + oluşturulmamışsa iş olmayan bir devreyi geçiştirecek kadarı oluşturulur. + Ardından sunucunun mevcut yükünü karşılamak için gereken sayıda çocuk + süreç oluşturulur. Bu suretle, kod her ikisi için de gereğini yerine + getirmeye çalışmış olur.</p> + + <p><code class="module"><a href="./mod/mod_status.html">mod_status</a></code> kullanıcıları <code>USR1</code> + gönderildiği zaman sunucu istatistiklerinin sıfırlanmadığı konusunda + uyarılacaktır. Kod, sunucunun yeni isteklere yanıt veremediği zamanı en + aza indirmenin yanısıra ayar parametrelerinize de uymak üzere + tasarlanmıştır (yeni istekler işletim sistemi tarafından kuyruğa + alınacağından bir istek kaybı olayı yaşanmaz). Bunu sağlamak için, her + iki kuşağın çocuklarının izini sürecek bir <em>çetele</em> tutulur.</p> + + <p><code class="module"><a href="./mod/mod_status.html">mod_status</a></code> modülü, nazikçe yeniden başlat komutunun + verilmesinden önce başlamış ve sunulmaya devam eden isteklere bakan + çocukları imlemek için ayrıca bir <code>G</code> (Graceful’un baş harfi) + kullanır.</p> + + <p>Günlük dosyası döndürme betiğine, yeniden başlatma öncesi günlüğe yazan + tüm çocukların işini bitirdiğini <code>USR1</code> kullanarak + bildirmenin bir yolu yoktur. Önerimiz, eski günlük kaydı üzerinde bir + işlem yapmaya başlamadan önce <code>USR1</code> sinyali gönderilmesinin + ardından belli bir süre beklenilmesi olacaktır. Örneğin, düşük band + genişliğine sahip istemcilere hizmet sunan çoğu sürecin işinin 10 + dakikadan önce bitmeyeceğini gözönüne alarak eski günlük üzerinde işlem + yapmaya başlamak için 15 dakika beklenebilir.</p> + + <div class="note"> + <p>Bir yeniden başlatma isteğinde, yapılandırma dosyalarında bir hata + olmadığından emin olmak için önce bir sözdizimi denetimi yapılır. Eğer + yapılandırma dosyalarınızda bir hata varsa bu sözdizimi hatasıyla ilgili + bir hata iletisi alırsınız ve sunucu yeniden başlamayı reddeder. Bu + yolla, bir hata sonucu sunucunun çökerek yeniden başlamaması nedeniyle + işlevsiz bir sunucuyla başbaşa kalmanız önlenmiştir.</p> + + <p>Ancak, bu hala sunucunuzun düzgünce yeniden başlatılmasını garanti + etmeyecektir. Yapılandırma dosyalarınızı sözdizimi denetiminin yanında + anlamlandırılması bakımından da sınamak için + <code class="program"><a href="./programs/httpd.html">httpd</a></code>’nin root olmayan bir kullanıcı tarafından + çalıştırılmasını deneyebilirsiniz. Eğer yapılandırma dosyalarında bir + hata yoksa soketleri ve günlük dosyalarını açmaya çalışırken root + aidiyetinde çalışmadığından veya çalışmakta olan asıl sunucu bu portları + zaten dinlediğinden başarısız olacaktır. Eğer başka bir sebeple + başarısız olursa olası sebep bir yapılandırma dosyası hatasıdır ve asıl + sunucuya ‘nazikçe yeniden başla’ komutunu vermeden önce bu hatayı + düzeltmeniz gerekir.</p></div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="hup" id="hup">Hemen Yeniden Başlat</a></h2> + + <dl><dt>Sinyal: HUP</dt> + <dd><code>apachectl -k restart</code></dd> + </dl> + + <p>Ana sürece <code>HUP</code> veya <code>restart</code> sinyalinin + gönderilmesi tüm çocukların <code>TERM</code> sinyali gönderilmiş gibi + öldürülmesine sebep olur fakat ana sürecin çıkmasını sağlamaz. + Ana süreç yapılandırma dosyalarını yeniden okur ve günlük kayıt + dosyalarını yeniden açar. Bunların ardından isteklere yanıt verecek yeni + kuşak çocukları oluşturmaya başlar.</p> + + <p><code class="module"><a href="./mod/mod_status.html">mod_status</a></code> kullanıcıları bir <code>HUP</code> sinyalı + gönderildiğinde sunucu istatistiklerinin sıfırlandığı konusunda + uyarılırlar.</p> + + <div class="note">‘Nazikçe yeniden başlat’ komutundaki gibi yeniden başlatma öncesi + bir sözdizimi denetimi yapılır. Eğer yapılandırma dosyalarınızda + sözdizimi hatası varsa yeniden başlatma işlemi gerçekleşmez ve sözdizimi + hatalarıyla ilgili bildirim alırsınız.</div> +</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> +<div class="section"> +<h2><a name="gracefulstop" id="gracefulstop">Nazikçe Durdur</a></h2> + + <dl><dt>Sinyal: WINCH</dt> + <dd><code>apachectl -k graceful-stop</code></dd> + </dl> + + <p>Ana sürecin <code>WINCH</code> veya <code>graceful-stop</code> + sinyalini alması, çocuklara ellerindeki mevcut işleri bitirdikten sonra + (veya sundukları bir şey yoksa hemen) çıkmalarının <em>önerilmesine</em> + sebep olur. Ana süreç bunun hemen ardından <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> dosyasını siler ve port + dinlemeyi keser. Ana süreç çalışmaya ve isteklere yanıt vermekte olan + çocuk süreçleri izlemeye devam eder. Tüm çocuklar işlerini bitirip + çıktığında veya <code class="directive"><a href="./mod/mpm_common.html#gracefulshutdowntimeout">GracefulShutdownTimeout</a></code> ile belirtilen + zaman aşımı dolduğunda ana süreç de kendini sonlandırır. Eğer zaman aşımı + devreye girmişse o an çalışmakta olan çocuk süreçlere <code>TERM</code> + sinyali gönderilerek hemen çıkmaları sağlanır.</p> + + <p>Bir <code>TERM</code> sinyali ile "graceful" durumundaki tüm çocuklar + ve ana süreç hemen sonlandırılacaktır. Bununla birlikte, <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> dosyası da silineceğinden, artık + <code>apachectl</code> veya <code>httpd</code>’yi bu sinyali göndermek + için kullanamayacaksınız.</p> + + <div class="note"><p><code>graceful-stop</code> sinyali, aynı anda, aynı yapılandırma + ile çok sayıda <code class="program"><a href="./programs/httpd.html">httpd</a></code> kopyasının çalıştırılabilmesine + imkan verir. Bu, Apache nazikçe yükseltileceği zaman güçlü bir özellik + haline gelmekteyse de, bazı yapılandırmalarda yarış koşullarının + oluşmasına ve kısır çekişmelere (deadlock) sebep olabilir.</p> + + <p>Sunucunun süreç kimliğini içeren kilit dosyaları (<code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code>) ve Unix soket dosyaları + (<code class="directive"><a href="./mod/mod_cgid.html#scriptsock">ScriptSock</a></code>) gibi dosyaların + disk üzerindeki mevcudiyetlerinin sorunsuz olarak devam ettiğinden emin + olunmaya çalışılmalıdır. Ayrıca, bir yapılandırma yönergesi, üçüncü + parti bir modül veya kalıcı CGI uygulamalarına ait disk kilit veya durum + dosyaları olabilir; <code class="program"><a href="./programs/httpd.html">httpd</a></code>’nin birden fazla kopyasının + çalışması nedeniyle bu dosyaların da üzerine yazılmadığından emin + olunmaya çalışılmalıdır.</p> + + <p><code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code> tarzı borulu günlükleme kullanımı gibi + durumlarda yarış koşullarının oluşması olasılığına karşı uyanık + olunmalıdır. Aynı günlük kayıt dosyalarını aynı anda döndürmeye çalışan + birden fazla <code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code> kopyasının çalıştırılması + halinde bunların her biri diğerlerinin günlük kayıt dosyalarının kaybına + sebep olabilir.</p></div> +</div></div> +<div class="bottomlang"> +<p><span>Mevcut Diller: </span><a href="./de/stopping.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | +<a href="./en/stopping.html" hreflang="en" rel="alternate" title="English"> en </a> | +<a href="./es/stopping.html" hreflang="es" rel="alternate" title="Español"> es </a> | +<a href="./fr/stopping.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | +<a href="./ja/stopping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="./ko/stopping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | +<a href="./tr/stopping.html" title="Türkçe"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Yorum</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> +<script type="text/javascript"><!--//--><![CDATA[//><!-- +var comments_shortname = 'httpd'; +var comments_identifier = 'http://httpd.apache.org/docs/2.4/stopping.html'; +(function(w, d) { + if (w.location.hostname.toLowerCase() == "httpd.apache.org") { + d.write('<div id="comments_thread"><\/div>'); + var s = d.createElement('script'); + s.type = 'text/javascript'; + s.async = true; + s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; + (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); + } + else { + d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); + } +})(window, document); +//--><!]]></script></div><div id="footer"> +<p class="apache">Copyright 2019 The Apache Software Foundation.<br /><a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> altında lisanslıdır.</p> +<p class="menu"><a href="./mod/">Modüller</a> | <a href="./mod/directives.html">Yönergeler</a> | <a href="http://wiki.apache.org/httpd/FAQ">SSS</a> | <a href="./glossary.html">Terimler</a> | <a href="./sitemap.html">Site Haritası</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- +if (typeof(prettyPrint) !== 'undefined') { + prettyPrint(); +} +//--><!]]></script> +</body></html>
\ No newline at end of file |