Introduction
by Joerg Stephan
Hi docs team,
my name is Joerg Stephan and i am an 34 year old system administrator
from Germany. I basically work on maintaining some hundreds of
debian/ubuntu based servers and a handful of centos machines. Besides my
administrator work i am also responsible for IT security questions.
I would like to join the docs project and contribute to fedora docs.
First i would like to start with the "CSI Security Policy" and
update/review and expand it, which was already topic on infrastructure
side. Than maybe translate it to German. Maybe someone can help me
finding the source and introduce me to docbook :-)
Cheers
--
Joerg Stephan
https://fedoraproject.org/wiki/User:Johe
10 years, 2 months
Fedora Docs Meeting Minutes 20JAN2014
by Pete Travis
====================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings
====================================================================================================
Meeting started by randomuser at 14:02:10 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-01-20/fedora_docs.20...
.
Meeting summary
---------------
* Roll Call (randomuser, 14:02:10)
* LINK: https://fedorahosted.org/fesco/ticket/1222 and
https://fedorahosted.org/fesco/ticket/1224 (jreznik, 14:09:56)
* jreznik's fedora.next jamboree (randomuser, 14:10:22)
* Publican4/Publishing (randomuser, 14:19:27)
* Koji is setup for accepting SRPMs but we're having problems getting
Koji to actually build them. We continue to troubleshoot.
(Sparks_too, 14:20:47)
* The new backend server is operational and is awaiting packages from
Koji to be setup completely. (Sparks_too, 14:21:26)
* We'll be running Publican 4 on the backend and RPMs will be made
available via the repos. (Sparks_too, 14:22:22)
* ACTION: Sparks to update publishing documentation. (Sparks_too,
14:30:31)
* Centos Docs (randomuser, 14:31:44)
* LINK: http://lists.centos.org/mailman/listinfo/centos-docs
(randomuser, 14:34:28)
* el7 and Fedora will have a lot in common, and centos has a docs
group (randomuser, 14:34:57)
* guides (randomuser, 14:39:32)
* Sparks is reworking the Security Guide, talk to him if you want to
help (randomuser, 14:52:53)
* LINK: https://fedoraproject.org/wiki/Category:Docs_Project_tasks
(randomuser, 14:55:41)
* use the task table to ask for and find tasks (randomuser, 14:55:59)
* Open Floor (randomuser, 14:57:53)
* ACTION: randomuser to send email to docs list about FAD scheduling
for weekend of 21MAR2014, give opportunity for protest (randomuser,
15:01:51)
* LINK: https://fedoraproject.org/wiki/Docs_FAD_2014 (randomuser,
15:04:50)
* ACTION: jhradilek to update docs FAD page for brno attendees
(randomuser, 15:06:21)
Meeting ended at 15:11:05 UTC.
Action Items
------------
* Sparks to update publishing documentation.
* randomuser to send email to docs list about FAD scheduling for weekend
of 21MAR2014, give opportunity for protest
* jhradilek to update docs FAD page for brno attendees
Action Items, by person
-----------------------
* jhradilek
* jhradilek to update docs FAD page for brno attendees
* randomuser
* randomuser to send email to docs list about FAD scheduling for
weekend of 21MAR2014, give opportunity for protest
* Sparks
* Sparks to update publishing documentation.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* randomuser (93)
* sgordon (26)
* Sparks_too (21)
* Sparks (19)
* jreznik (15)
* pbokoc (13)
* jjmcd (8)
* lnovich (8)
* jhradilek (7)
* Capesteve (7)
* zodbot (6)
* roshi (2)
* ciupicri (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
10 years, 2 months
Docs FAD Scheduling - 21-23MAR2014
by Pete Travis
After collecting survey responses and conversations, a preferred date
for the 2014 Fedora Docs Activity Day has emerged.
Assuming no objections, the FAD will take place on 21MAR, 22MAR, and
23MAR your choice of Raleigh or Brno. This means you - reply here if
you want us to reschedule, and reply soon.
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
10 years, 2 months
Fedora Docs Meeting Reminder 20JAN2014 1400UTC
by Pete Travis
Join your Fedora Docs friends in #fedora-meeting for a keyboard mashing
contest, Monday at 1400UTC. The one with most intelligible output wins,
or failing that, the one with the most amusing monkey keyboard operators
will win.
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
10 years, 2 months
Re: Did you receive my previous email with attachment?
by Pete Travis
On Jan 17, 2014 5:11 AM, "Leslie S Satenstein" <lsatenstein(a)yahoo.com>
wrote:
>
> This was the contents with attachment. If you cannot receive attachments,
I will provide a link to the file via my Dropbox.
>
>
> Hi Guys, Pete
>
> I copied and pasted the draft from the web into a libreoffice document.
> Using markup management and comments that are standard with a word
processor, I marked up the first six sections.
>
> I would continue, but before I spend a day or two more time, I would like
feedback on what I did.
>
> If you are not familiar with markups and comments, here is a brief
description.
> Turn on markups via the edit command. Every change to the document is
identified and as well, a revision bar is written to the left margin.
> If there is a section of the document that needs clarification, highlight
it and use the insert comment command to put a comment to the right side
of the document, The comment and the highlighted text go together.
>
> For the person reviewing the changes.
> You can turn off markup,
> Now, as you pass through the document, you can accept or reject each
change. Ditto for the comment. You can choose to leave it there or remove
it.
> You could also continue with markups, marking up my changes or adding
your own. Each set of markups will be identified by the person making them
and with a timestamp.
>
> One could also click to select and accept all changes. That would result
in a clean updated document which can be pasted back into the website.
>
> This iteration of markup, review, and redo typically takes three
iterations and the result will be a superb document, easy to translate.
>
> Please review the attached and email me back with your changes or
comments. Let me know if I should continue to the end of the guide.
>
>
> Thanks in advance
>
>
>
> Regards
>
> Leslie
>
> Regards
>
> Leslie
> Mr. Leslie Satenstein
> An experienced Information Technology specialist.
> Yesterday was a good day, today is a better day,
> and tomorrow will be even better.
> lsatenstein(a)yahoo.com
> SENT FROM MY OPEN SOURCE LINUX SYSTEM.
>
Hi Leslie,
I did see your mail and attachment, but haven't had time to look it over
yet. You sent that mail only to me, btw , not the list - you wanted
reply-to-all I think :) Also, attachments will probably be rejected by the
list, so it would be better to post a link to the file and best to just use
the body of the email for your feedback.
While we are on the subject, have you given any consideration to using git
and editing source like the rest of us? Frankly, your method creates a lot
oof extra work for you and for me ( or whoever looks at your review ). I
am well acquainted with your personal and professional history at this
point, but I don't understand why you refuse to follow the established
workflow. If you were to follow the git-branch-work-commit process, your
changes would be readily apparent, your justification/comments would fit
nicely in the commit message, and applying your changes would require
*nearly zero effort* . If the suggested change is in an ODF, applying
changes requires the additional step of manually editing the source. Then,
we have to build and published the updated document for you to see any
changes; that's a lot of extra work and you could just type `git pull` and
save us from it.
I recently added a section to the documentation guide[1] on creating a
patch using git. As someone with experience in a very different workflow,
your review of *that* content[2] would be especially welcome.
[1]
http://fedorapeople.org/groups/docs/docs-guide/sect-workflow-patching.html
[2] https://git.fedorahosted.org/cgit/docs/documentation-guide.git
--Pete
10 years, 3 months
Update on new docs.fp.o website rollout and publishing process change
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Greetings Docs Folks,
I just had a great conversation with Rudi[0] about what is still needed to move our publishing process from what it is now to what we hope it will be. As of this moment we are *very* close to having this fixed. The new server for docs.fp.o exists and is just waiting for Koji to start producing RPMs. Koji is all but finished, now, only requiring a configuration change to allow SRPMs to be build for our repo. Once the RPMs are there we'll need to configure the server to 'yum install' those packages (documents). Once that is complete we'll rsync them to the proxies and all will be right with the world.
This week I'll be working with Release Engineering to try to get the Koji piece finished. As soon as that is complete we'll be able to start testing.
Rudi is also working on packaging up Publican 4 which will be the basis for the server. We'll need to make sure everyone upgrades and uses that for the new site. This shouldn't be a problem for those running >= Fedora 19. Those running RHEL or CentOS will need to install from the options repo(?).
Hopefully this will be a (mostly) painless transition that will be far more bullet proof than what we've got now.
If you have any questions feel free to ping me on IRC or respond to this email.
[0] For those that don't know Rudi, he's our liaison (and really great guy) to Red Hat Content Engineering and upstream Publican.
- -- Eric
- --------------------------------------------------
Eric "Sparks" Christensen
Fedora Project
sparks(a)fedoraproject.org - sparks(a)redhat.com
097C 82C3 52DF C64A 50C2 E3A3 8076 ABDE 024B B3D1
- --------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQGcBAEBCgAGBQJS1KFhAAoJEB/kgVGp2CYv8fUL/Rjl4h74KlhyC4djCD0K/El7
tPd+aU8PzQgqB1STHl1VKIVYdwbmIOQ3qnPtOoyGScqtEnpouqLNkaNcq0Deva9N
+v7/jDMDk3kjz5rKNPhREwHX6gc27M5+CA71FgACKNaI2dYYgg3O7GHO/CUPMhkl
6fGJFqUyuQEe41ise3/eRcje/d/066CbLKKADb16ZbEcUCEE6c7TqG9AfUH1bz9D
EwQmge/IGJevNscE0GZur4sqSEX0LZ4zbKsoqrb2L6IMVC35xAqntOadfgSEbbtw
+rBV9X0f404yjBF9ao+Pl6WEtZtL825B8cBhrmznZZalKB9tqP64+6jLUWysLDeH
DQ2+n1zhCtmsNo6UfcEq25P9cy5rTeYa/BE754tQay+WugyBmH3kzK6I/oHd3WcU
+Rw8z7wq3+yueW5l41tnTvElnCSMbYQ62hmAbmMqxcdlIJir59VbSlXvEUc27ObG
JdMdawnhIoWiVKbgV9CuqWSntU1+TfoAWpn6+mSnFw==
=bKKI
-----END PGP SIGNATURE-----
10 years, 3 months
Fedora Docs Meeting Summary 13Jan2013
by Pete Travis
====================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
https://fedoraproject.org/wiki/Docs_Project_meetings
====================================================================================================
Meeting started by randomuser at 14:00:18 UTC. The full logs are
available athttp://meetbot.fedoraproject.org/fedora-meeting/2014-01-13/fedora_docs....
.
Meeting summary
---------------
* Roll Call (randomuser, 14:00:18)
* Guide Status (randomuser, 14:07:19)
* pbokoc has updated IG for f20 and is prepping POTs now (randomuser,
14:07:53)
* LINK:
https://fedoraproject.org/wiki/Category:Docs_Project_tasks?rd=Docs_Projec...
(randomuser, 14:14:03)
* If you have or want tasks, use the tasks page (randomuser,
14:14:15)
* Capesteve is creating a Networking Guide, starting with Networking
content from Sysadmin guide (randomuser, 14:26:04)
* LINK:
https://git.fedorahosted.org/cgit/docs/power-management-guide.git/plain/p...
(pbokoc, 14:26:22)
* Publican4 thing (randomuser, 14:30:43)
* Docs FAD (randomuser, 14:36:40)
* nb nominates randomuser to continue as docs lead (nb, 14:48:09)
* ACTION: randomuser to send mail to list regarding 21MAR-23MAR FAD
scheduling (randomuser, 14:49:51)
* bz tickets (randomuser, 14:51:21)
Meeting ended at 15:00:17 UTC.
Action Items
------------
* randomuser to send mail to list regarding 21MAR-23MAR FAD scheduling
Action Items, by person
-----------------------
* randomuser
* randomuser to send mail to list regarding 21MAR-23MAR FAD scheduling
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* randomuser (86)
* pbokoc (25)
* Sparks (19)
* yruseva (13)
* jjmcd (9)
* misc (7)
* lnovich (6)
* nb (6)
* zodbot (4)
* Capesteve (4)
* pkovar (2)
* gomix (1)
* jhradilek (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
10 years, 3 months
Fedora Docs Meeting Reminder 13JAN2013
by Pete Travis
What: Fedora Documentation Project Meeting
When: 1400UTC 13JAN2013
Where: #fedora-meeting on Freenode
Why: Discussion of Fedora Docs stuff
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
10 years, 3 months
Publican --build, html files are incorrect
by Tiansworld
Hi everyone,
I was trying to publish the updated cs-CZ and zh_CN translation of Burning
ISO to disc. There are untranslated strings in section 5.2.1.3 on both
languages.
But I found the built html files are not correct, not the content, but the
appearance. When I open the generated html files in browser, they only show
almost plain text, no CSS file loaded and no navigation menu were shown.
However, the PDF files are OK.
My procedure is:
publican clean (I've built them few days before)
publican build --embedtoc --publish --formats epub,html,html-single,pdf
--langs cs-CZ, zh-CN
Another issue is happend when I tried to install them:
$publican install_book --site_config ../../fedoradocs/web/homepage.cfg
--lang cs-CZ
DEBUG: Publican: config loaded
DBD::SQLite::db do failed: no such column: formats at
/usr/share/perl5/vendor_perl/Publican/WebSite.pm line 433, <FH> line 14.
DBD::SQLite::db prepare failed: no such column: formats at
/usr/share/perl5/vendor_perl/Publican/WebSite.pm line 539, <FH> line 14.
Can't call method "execute" on an undefined value at
/usr/share/perl5/vendor_perl/Publican/WebSite.pm line 540, <FH> line 14.
What should I do to fix these?
Regards
Tiansworld
Fedora Project Contributor
10 years, 3 months
[system-administrators-guide] Update the Apache chapter
by Rashadul Islam
---
en-US/The_Apache_HTTP_Server.xml | 110 +++++++++++++++++++++++++++++-
---------
1 file changed, 83 insertions(+), 27 deletions(-)
diff --git a/en-US/The_Apache_HTTP_Server.xml b/en-US/The_Apache_HTTP_
Server.xml
index d64c8e9..7f74d6b 100644
--- a/en-US/The_Apache_HTTP_Server.xml
+++ b/en-US/The_Apache_HTTP_Server.xml
@@ -8,20 +8,20 @@
<see><application>Apache HTTP Server</application></see>
</indexterm>
<para>
- This section focuses on the <application>Apache HTTP Server
2.2</application>, a robust, full-featured open source web server developed
by the <ulink url="http://www.apache.org/">Apache Software
Foundation</ulink>, that is included in &MAJOROSVER;. It describes the
basic configuration of the <systemitem class="service">httpd</systemitem>
service, and covers advanced topics such as adding server modules, setting
up virtual hosts, or configuring the secure HTTP server.
+ This section focuses on the <application>Apache HTTP Server
2.4</application>, a robust, full-featured open source web server developed
by the <ulink url="http://www.apache.org/">Apache Software
Foundation</ulink>, that is included in &MAJOROSVER;. It describes the
basic configuration of the <systemitem class="service">httpd</systemitem>
service, and covers advanced topics such as adding server modules, setting
up virtual hosts, or configuring the secure HTTP server.
</para>
<para>
- There are important differences between the Apache HTTP Server 2.2 and
version 2.0, and if you are upgrading from a previous release of &MAJOROS;,
you will need to update the <systemitem class="service">httpd</systemitem>
service configuration accordingly. This section reviews some of the newly
added features, outlines important changes, and guides you through the
update of older configuration files.
+ There are important differences between the Apache HTTP Server 2.2 and
version 2.4, and if you are upgrading from a previous release of &MAJOROS;,
you will need to update the <systemitem class="service">httpd</systemitem>
service configuration accordingly. This section reviews some of the newly
added features, outlines important changes, and guides you through the
update of older configuration files.
</para>
<section id="s2-apache-version2-features">
<title>New Features</title>
<indexterm>
<primary><application>Apache HTTP Server</application></primary>
- <secondary>version 2.2</secondary>
+ <secondary>version 2.4</secondary>
<tertiary>features</tertiary>
</indexterm>
<para>
- The Apache HTTP Server version 2.2 introduces the following
enhancements:
+ The Apache HTTP Server version 2.4 introduces the following
enhancements:
</para>
<itemizedlist>
<listitem>
@@ -59,18 +59,70 @@
A new structure for authentication and authorization support,
replacing the authentication modules provided in previous versions.
</para>
</listitem>
+ <listitem>
+ <para>
+ Multiple MPMs can now be built as loadable modules at compile
time. The MPM of choice can be configured at run time.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <indexterm>
+ <primary><application>Apache HTTP
Server</application></primary>
+ <secondary>core enhancements</secondary>
+ <tertiary><systemitem class="resource">LogLevel</
systemitem></tertiary>
+ </indexterm>
+ The LogLevel can now be configured per module and per directory.
New levels trace1 to trace8 have been added above the debug log level.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <indexterm>
+ <primary><application>Apache HTTP
Server</application></primary>
+ <secondary>core enhancements</secondary>
+ <tertiary><systemitem class="resource">SetEnvIfExpr<
/systemitem></tertiary>
+ </indexterm>
+ <indexterm>
+ <primary><application>Apache HTTP
Server</application></primary>
+ <secondary>core enhancements</secondary>
+ <tertiary><systemitem class="resource">RewriteCond</
systemitem></tertiary>
+ </indexterm>
+ A new expression parser allows to specify complex conditions using
a common syntax in directives like <systemitem
class="resource">SetEnvIfExpr</systemitem>, <systemitem
class="resource">RewriteCond</systemitem>, Header, If, and others. +
</para>
+ </listitem>
+ <listitem>
+ <para>
+ <indexterm>
+ <primary><application>Apache HTTP
Server</application></primary>
+ <secondary>core enhancements</secondary>
+ <tertiary><systemitem class="resource">.htaccess</
systemitem></tertiary>
+ </indexterm>
+ The new AllowOverrideList directive allows more fine grained
control which directives are allowed in <systemitem
class="resource">.htaccess</systemitem> files. + </para>
+ </listitem>
+<listitem>
+ <para>
+ <indexterm>
+ <primary><application>Apache HTTP
Server</application></primary>
+ <secondary>core enhancements</secondary>
+ <tertiary>Reduced memory usage</tertiary>
+ </indexterm>
+ Apache 2.4.x tends to use less memory than 2.2.x. + </para>
+ </listitem>
</itemizedlist>
</section>
<section id="s2-apache-version2-changes">
<title>Notable Changes</title>
<indexterm>
<primary><application>Apache HTTP Server</application></primary>
- <secondary>version 2.2</secondary>
+ <secondary>version 2.4</secondary>
<tertiary>changes</tertiary>
</indexterm>
<para>
- Since version 2.0, few changes have been made to the default
<systemitem class="service">httpd</systemitem> service configuration:
+ Since version 2.4, few changes have been made to the default
<systemitem class="service">httpd</systemitem> service configuration:
</para>
+
+ <!-- Need review here till line 151 -->
<itemizedlist>
<listitem>
<para>
@@ -98,16 +150,17 @@
</para>
</listitem>
</itemizedlist>
+
</section>
<section id="s2-apache-version2-migrating">
<title>Updating the Configuration</title>
<indexterm>
<primary><application>Apache HTTP Server</application></primary>
- <secondary>version 2.2</secondary>
- <tertiary>updating from version 2.0</tertiary>
+ <secondary>version 2.4</secondary>
+ <tertiary>updating from version 2.4</tertiary>
</indexterm>
<para>
- To update the configuration files from the Apache HTTP Server
version 2.0, take the following steps:
+ To update the configuration files from the Apache HTTP Server
version 2.4, take the following steps:
</para>
<procedure>
<step>
@@ -141,7 +194,7 @@
</para>
<screen><command>service httpd configtest</command></screen>
<para>
- For more information on upgrading the Apache HTTP Server
configuration from version 2.0 to 2.2, refer to <ulink url="
http://httpd.apache.org/docs/2.2/upgrading.html" />.
+ For more information on upgrading the Apache HTTP Server
configuration from version 2.2 to 2.4, refer to <ulink url="
http://httpd.apache.org/docs/2.4/upgrading.html" />.
</para>
</section>
<section id="s2-apache-running">
@@ -223,6 +276,8 @@
This will cause the running <systemitem
class="service">httpd</systemitem>
service to reload the configuration file. Note that any requests being
currently processed will be interrupted, which may cause a client browser
to display an error message or render a partial page.
</para>
</listitem>
+
+ <!-- Require to review till line 288-->
<listitem>
<para>
To reload the configuration without affecting active requests,
run the following command as <systemitem class="username">root</systemitem>:
@@ -233,6 +288,7 @@
</para>
</listitem>
</orderedlist>
+
<para>
Refer to <xref linkend="ch-Services_and_Daemons" /> for more
information on how to configure services in &MAJOROS;.
</para>
@@ -2987,7 +3043,7 @@ ErrorDocument 404 /404-not_found.html</programlisting>
<option>Minor</option>
</entry>
<entry>
- Includes the product name and the minor version of
the server (for example, <literal>2.2</literal>).
+ Includes the product name and the minor version of
the server (for example, <literal>2.4</literal>).
</entry>
</row>
<row>
@@ -2995,7 +3051,7 @@ ErrorDocument 404 /404-not_found.html</programlisting>
<option>Min</option>
</entry>
<entry>
- Includes the product name and the minimal version of
the server (for example, <literal>2.2.15</literal>).
+ Includes the product name and the minimal version of
the server (for example, <literal>2.4.15</literal>).
</entry>
</row>
<row>
@@ -3407,21 +3463,21 @@ ErrorDocument 404 /404-not_found.html</
programlisting>
<indexterm>
<primary><application>Apache HTTP
Server</application></primary>
<secondary>directives</secondary>
- <tertiary><option>MaxClients</option></tertiary>
+ <tertiary><option>MaxRequestWorkers</option></tertiary>
</indexterm>
- <option>MaxClients</option>
+ <option>MaxRequestWorkers</option>
</term>
<listitem>
<para>
- The <option>MaxClients</option> directive allows you to
specify the maximum number of simultaneously connected clients to process
at one time. It takes the following form:
+ The <option>MaxRequestWorkers</option> directive allows you
to specify the maximum number of simultaneously connected clients to
process at one time. It takes the following form:
</para>
- <programlisting>MaxClients <replaceable>number</
replaceable></programlisting>
+ <programlisting>MaxRequestWorkers <replaceable>number</
replaceable></programlisting>
<para>
A high <replaceable>number</replaceable> can improve the
performance of the server, although it is not recommended to exceed
<literal>256</literal> when using the <systemitem
class="resource">prefork</systemitem>
MPM.
</para>
- <example id="example-apache-mpm-maxclients">
- <title>Using the MaxClients directive</title>
- <programlisting>MaxClients 256</programlisting>
+ <example id="example-apache-mpm-maxrequestworkers">
+ <title>Using the MaxRequestWorkers directive</title>
+ <programlisting>MaxRequestWorkers 256</programlisting>
</example>
</listitem>
</varlistentry>
@@ -3430,24 +3486,24 @@ ErrorDocument 404 /404-not_found.html</
programlisting>
<indexterm>
<primary><application>Apache HTTP
Server</application></primary>
<secondary>directives</secondary>
- <tertiary><option>MaxClients</option></tertiary>
+ <tertiary><option>MaxRequestWorkers</option></tertiary>
</indexterm>
- <option>MaxRequestsPerChild</option>
+ <option> MaxConnectionsPerChild</option>
</term>
<listitem>
<para>
- The <option>MaxRequestsPerChild</option> directive allows
you to specify the maximum number of request a child process can serve
before it dies. It takes the following form:
+ The <option> MaxConnectionsPerChild</option> directive
allows you to specify the maximum number of request a child process can
serve before it dies. It takes the following form:
</para>
- <programlisting>MaxRequestsPerChild <replaceable>number</
replaceable></programlisting>
+ <programlisting> MaxConnectionsPerChild <replaceable>number</
replaceable></programlisting>
<para>
Setting the <replaceable>number</replaceable> to
<literal>0</literal> allows unlimited number of requests.
</para>
<para>
- The <option>MaxRequestsPerChild</option> directive is used
to prevent long-lived processes from causing memory leaks.
+ The <option> MaxConnectionsPerChild</option> directive is
used to prevent long-lived processes from causing memory leaks.
</para>
- <example id="example-apache-mpm-maxrequestsperchild">
- <title>Using the MaxRequestsPerChild directive</title>
- <programlisting>MaxRequestsPerChild 4000</programlisting>
+ <example id="example-apache-mpm-maxconnectionsperchild">
+ <title>Using the MaxConnectionsPerChild directive</title>
+ <programlisting> MaxConnectionsPerChild 4000</programlisting>
</example>
</listitem>
</varlistentry>
--
1.8.4.2
10 years, 3 months
