From: André Malo Date: Wed, 10 Jun 2020 21:25:03 +0000 (+0000) Subject: update X-Git-Tag: 2.4.44~91 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d7ae4aa2ee2faa8fa802f5e63aae6c299ffa2f24;p=thirdparty%2Fapache%2Fhttpd.git update git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1878727 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/man/rotatelogs.8 b/docs/man/rotatelogs.8 index 6baaf140e96..eba61bcc5b8 100644 --- a/docs/man/rotatelogs.8 +++ b/docs/man/rotatelogs.8 @@ -19,7 +19,7 @@ .el .ne 3 .IP "\\$1" \\$2 .. -.TH "ROTATELOGS" 8 "2018-07-06" "Apache HTTP Server" "rotatelogs" +.TH "ROTATELOGS" 8 "2020-06-10" "Apache HTTP Server" "rotatelogs" .SH NAME rotatelogs \- Piped logging program to rotate Apache logs @@ -44,7 +44,7 @@ rotatelogs \- Piped logging program to rotate Apache logs Causes the use of local time rather than GMT as the base for the interval or for \fBstrftime(3)\fR formatting with size-based rotation\&. .TP \fB-L\fR \fIlinkname\fR -Causes a hard link to be made from the current logfile to the specified link name\&. This can be used to watch the log continuously across rotations using a command like \fBtail -F linkname\fR\&. +.PP Causes a hard link to be made from the current logfile to the specified link name\&. This can be used to watch the log continuously across rotations using a command like \fBtail -F linkname\fR\&. .PP If the linkname is not an absolute path, it is relative to \fBrotatelogs\fR' working directory, which is the ServerRoot when \fBrotatelogs\fR is run by the server\&. .TP \fB-p\fR \fIprogram\fR If given, \fBrotatelogs\fR will execute the specified program every time a new log file is opened\&. The filename of the newly opened file is passed as the first argument to the program\&. If executing after a rotation, the old log file is passed as the second argument\&. \fBrotatelogs\fR does not wait for the specified program to terminate before continuing to operate, and will not log any error code returned on termination\&. The spawned program uses the same stdin, stdout, and stderr as rotatelogs itself, and also inherits the environment\&. @@ -71,7 +71,7 @@ Create log file for each interval, even if empty\&. Use a circular list of filenames without timestamps\&. With -n 3, the series of log files opened would be "logfile", "logfile\&.1", "logfile\&.2", then overwriting "logfile"\&. Available in 2\&.4\&.5 and later\&. .TP \fB\fIlogfile\fR\fR -.PP The path plus basename of the logfile\&. If \fIlogfile\fR includes any '%' characters, it is treated as a format string for \fBstrftime(3)\fR\&. Otherwise, the suffix \fI\&.nnnnnnnnnn\fR is automatically added and is the time in seconds (unless the -t option is used)\&. Both formats compute the start time from the beginning of the current period\&. For example, if a rotation time of 86400 is specified, the hour, minute, and second fields created from the \fBstrftime(3)\fR format will all be zero, referring to the beginning of the current 24-hour period (midnight)\&. .PP When using \fBstrftime(3)\fR filename formatting, be sure the log file format has enough granularity to produce a different file name each time the logs are rotated\&. Otherwise rotation will overwrite the same file instead of starting a new one\&. For example, if \fIlogfile\fR was \fB/var/log/errorlog\&.%Y-%m-%d\fR with log rotation at 5 megabytes, but 5 megabytes was reached twice in the same day, the same log file name would be produced and log rotation would keep writing to the same file\&. +.PP The path plus basename of the logfile\&. If \fIlogfile\fR includes any '%' characters, it is treated as a format string for \fBstrftime(3)\fR\&. Otherwise, the suffix \fI\&.nnnnnnnnnn\fR is automatically added and is the time in seconds (unless the -t option is used)\&. Both formats compute the start time from the beginning of the current period\&. For example, if a rotation time of 86400 is specified, the hour, minute, and second fields created from the \fBstrftime(3)\fR format will all be zero, referring to the beginning of the current 24-hour period (midnight)\&. .PP When using \fBstrftime(3)\fR filename formatting, be sure the log file format has enough granularity to produce a different file name each time the logs are rotated\&. Otherwise rotation will overwrite the same file instead of starting a new one\&. For example, if \fIlogfile\fR was \fB/var/log/errorlog\&.%Y-%m-%d\fR with log rotation at 5 megabytes, but 5 megabytes was reached twice in the same day, the same log file name would be produced and log rotation would keep writing to the same file\&. .PP If the logfile is not an absolute path, it is relative to \fBrotatelogs\fR' working directory, which is the ServerRoot when \fBrotatelogs\fR is run by the server\&. .TP \fB\fIrotationtime\fR\fR The time between log file rotations in seconds\&. The rotation occurs at the beginning of this interval\&. For example, if the rotation time is 3600, the log file will be rotated at the beginning of every hour; if the rotation time is 86400, the log file will be rotated every night at midnight\&. (If no data is logged during an interval, no file will be created\&.) diff --git a/docs/manual/convenience.map b/docs/manual/convenience.map index 6942c043d9b..b8dc1fe5058 100644 --- a/docs/manual/convenience.map +++ b/docs/manual/convenience.map @@ -172,7 +172,10 @@ chrootdir mod/mod_unixd.html#chrootdir contentdigest mod/core.html#contentdigest cookiedomain mod/mod_usertrack.html#cookiedomain cookieexpires mod/mod_usertrack.html#cookieexpires +cookiehttponly mod/mod_usertrack.html#cookiehttponly cookiename mod/mod_usertrack.html#cookiename +cookiesamesite mod/mod_usertrack.html#cookiesamesite +cookiesecure mod/mod_usertrack.html#cookiesecure cookiestyle mod/mod_usertrack.html#cookiestyle cookietracking mod/mod_usertrack.html#cookietracking coredumpdirectory mod/mpm_common.html#coredumpdirectory @@ -374,16 +377,19 @@ maxrequestworkers mod/mpm_common.html#maxrequestworkers maxspareservers mod/prefork.html#maxspareservers maxsparethreads mod/mpm_common.html#maxsparethreads maxthreads mod/mpm_netware.html#maxthreads +mdactivationdelay mod/mod_md.html#mdactivationdelay mdbaseserver mod/mod_md.html#mdbaseserver mdcachallenges mod/mod_md.html#mdcachallenges mdcertificateagreement mod/mod_md.html#mdcertificateagreement mdcertificateauthority mod/mod_md.html#mdcertificateauthority +mdcertificatecheck mod/mod_md.html#mdcertificatecheck mdcertificatefile mod/mod_md.html#mdcertificatefile mdcertificatekeyfile mod/mod_md.html#mdcertificatekeyfile mdcertificatemonitor mod/mod_md.html#mdcertificatemonitor mdcertificateprotocol mod/mod_md.html#mdcertificateprotocol mdcertificatestatus mod/mod_md.html#mdcertificatestatus mdchallengedns01 mod/mod_md.html#mdchallengedns01 +mdcontactemail mod/mod_md.html#mdcontactemail mddrivemode mod/mod_md.html#mddrivemode mdhttpproxy mod/mod_md.html#mdhttpproxy mdmember mod/mod_md.html#mdmember diff --git a/docs/manual/howto/cgi.html.en b/docs/manual/howto/cgi.html.en index 73b9609d1d5..e026d8efe57 100644 --- a/docs/manual/howto/cgi.html.en +++ b/docs/manual/howto/cgi.html.en @@ -546,7 +546,7 @@ foreach my $key (keys %ENV) {

If you're writing CGI programs in C, there are a variety of options. One of these is the CGIC library, from - http://www.boutell.com/cgic/.

+ https://web.mit.edu/wwwdev/www/cgic.html.

top

For more information

diff --git a/docs/manual/howto/cgi.html.es b/docs/manual/howto/cgi.html.es index 6529c768b7e..8121cd964e9 100644 --- a/docs/manual/howto/cgi.html.es +++ b/docs/manual/howto/cgi.html.es @@ -29,6 +29,10 @@  ja  |  ko 

+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
Support Apache!
+
Cette traduction peut être périmée. Vérifiez la version + anglaise pour les changements récents.
Support Apache!