archive-fr.com » FR » O » OBSPM.FR

Total: 155

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • logresolve - Resolve IP-addresses to hostnames in Apache log files - Apache HTTP Server
    hash table cache This means that each IP number will only be looked up the first time it is found in the log file Takes an Apache log file on standard input The IP addresses must be the first thing on each line and must be seperated from the remainder of the line by a space Synopsis Options Synopsis logresolve s filename c access log access log new Options s

    Original URL path: http://ama09.obspm.fr/manual-2.0/programs/logresolve.html (2015-11-16)
    Open archived version from archive


  • rotatelogs - Piped logging program to rotate Apache logs - Apache HTTP Server
    logfile 5M common This configuration will rotate the logfile whenever it reaches a size of 5 megabytes Synopsis Options Portability Synopsis rotatelogs logfile rotationtime offset filesize M Options logfile The path plus basename of the logfile If logfile includes any characters it is treated as a format string for strftime 3 Otherwise the suffix nnnnnnnnnn is automatically added and is the time in seconds Both formats compute the start time from the beginning of the current period rotationtime The time between log file rotations in seconds offset The number of minutes offset from UTC If omitted zero is assumed and UTC is used For example to use local time in the zone UTC 5 hours specify a value of 300 for this argument filesize M The maximum file size in megabytes followed by the letter M to specify size rather than time Use this parameter in place of both rotationtime and offset Portability The following logfile format string substitutions should be supported by all strftime 3 implementations see the strftime 3 man page for library specific extensions A full weekday name localized a 3 character weekday name localized B full month name localized b 3 character month name localized c

    Original URL path: http://ama09.obspm.fr/manual-2.0/programs/rotatelogs.html (2015-11-16)
    Open archived version from archive

  • suexec - Switch user before executing external programs - Apache HTTP Server
    to achieve this it must run as root Since the HTTP daemon normally doesn t run as root the suexec executable needs the setuid bit set and must be owned by root It should never be writable for any other person than root For further information about the concepts and and the security model of suexec please refer to the suexec documentation http httpd apache org docs 2 0 suexec

    Original URL path: http://ama09.obspm.fr/manual-2.0/programs/suexec.html (2015-11-16)
    Open archived version from archive

  • Other Programs - Apache HTTP Server
    perl script is designed to be run at a frequent interval by something like cron It connects to the server and downloads the status information It reformats the information to a single line and logs it to a file Adjust the variables at the top of the script to specify the location of the resulting logfile split logfile This perl script will take a combined Web server access log file

    Original URL path: http://ama09.obspm.fr/manual-2.0/programs/other.html (2015-11-16)
    Open archived version from archive

  • International Customized Server Error Messages - Apache HTTP Server
    the configuration we defined the names for the error documents to be just their error number without any suffix The names of the individual error documents are now determined like this I m using 403 as an example think of it as a placeholder for any of the configured error documents No file errordocs 403 should exist Otherwise it would be found and served with the DefaultType usually text plain all negotiation would be bypassed For each language for which we have an internationalized version note that this need not be the same set of languages for each error code you can get by with a single language version until you actually have translated versions a document errordocs 403 shtml lang is created and filled with the error text in that language see below One fallback document called errordocs 403 shtml is created usually by creating a symlink to the default language variant see below The Common Header and Footer Files By putting as much layout information in two special include files the error documents can be reduced to a bare minimum One of these layout files defines the HTML document header and a configurable list of paths to the icons to be shown in the resulting error document These paths are exported as a set of SSI environment variables and are later evaluated by the footer special file The title of the current error which is put into the TITLE tag and an H1 header is simply passed in from the main error document in a variable called title By changing this file the layout of all generated error messages can be changed in a second By exploiting the features of SSI you can easily define different layouts based on the current virtual host or even based on the client s domain name The second layout file describes the footer to be displayed at the bottom of every error message In this example it shows an apache logo the current server time the server version string and adds a mail reference to the site s webmaster For simplicity the header file is simply called head shtml because it contains server parsed content but no language specific information The footer file exists once for each language translation plus a symlink for the default language for English French and German versions default english foot shtml en foot shtml fr foot shtml de foot shtml symlink to foot shtml en Both files are included into the error document by using the directives include virtual head and include virtual foot respectively the rest of the magic occurs in mod negotiation and in mod include See the listings below to see an actual HTML implementation of the discussed example Creating ErrorDocuments in Different Languages After all this preparation work little remains to be said about the actual documents They all share a simple common structure set var title value error description title include virtual head explanatory error text include virtual foot In the listings

    Original URL path: http://ama09.obspm.fr/manual-2.0/misc/custom_errordocs.html (2015-11-16)
    Open archived version from archive

  • Connections in the FIN_WAIT_2 state and Apache - Apache HTTP Server
    any data sent by the client for a certain time after the server closes the connection The exact reasons for doing this are somewhat complicated but involve what happens if the client is making a request at the same time the server sends a response and closes the connection Without lingering the client might be forced to reset its TCP input buffer before it has a chance to read the server s response and thus understand why the connection has closed See the appendix for more details The code in lingering close appears to cause problems for a number of factors including the change in traffic patterns that it causes The code has been thoroughly reviewed and we are not aware of any bugs in it It is possible that there is some problem in the BSD TCP stack aside from the lack of a timeout for the FIN WAIT 2 state exposed by the lingering close code that causes the observed problems What Can I Do About it There are several possible workarounds to the problem some of which work better than others Add a timeout for FIN WAIT 2 The obvious workaround is to simply have a timeout for the FIN WAIT 2 state This is not specified by the RFC and could be claimed to be a violation of the RFC but it is widely recognized as being necessary The following systems are known to have a timeout FreeBSD versions starting at 2 0 or possibly earlier NetBSD version 1 2 OpenBSD all versions BSD OS 2 1 with the K210 027 patch installed Solaris as of around version 2 2 The timeout can be tuned by using ndd to modify tcp fin wait 2 flush interval but the default should be appropriate for most servers and improper tuning can have negative impacts Linux 2 0 x and earlier HP UX 10 x defaults to terminating connections in the FIN WAIT 2 state after the normal keepalive timeouts This does not refer to the persistent connection or HTTP keepalive timeouts but the SO LINGER socket option which is enabled by Apache This parameter can be adjusted by using nettune to modify parameters such as tcp keepstart and tcp keepstop In later revisions there is an explicit timer for connections in FIN WAIT 2 that can be modified contact HP support for details SGI IRIX can be patched to support a timeout For IRIX 5 3 6 2 and 6 3 use patches 1654 1703 and 1778 respectively If you have trouble locating these patches please contact your SGI support channel for help NCR s MP RAS Unix 2 xx and 3 xx both have FIN WAIT 2 timeouts In 2 xx it is non tunable at 600 seconds while in 3 xx it defaults to 600 seconds and is calculated based on the tunable max keep alive probes default of 8 multiplied by the keep alive interval default 75 seconds Sequent s ptx TCP IP for DYNIX

    Original URL path: http://ama09.obspm.fr/manual-2.0/misc/fin_wait_2.html (2015-11-16)
    Open archived version from archive

  • Known Problems in Clients - Apache HTTP Server
    Networks also exhibits this problem However they have fixed it in version 4 01 of the player but version 4 01 uses the same User Agent as version 4 0 The workaround is still BrowserMatch RealPlayer 4 0 force response 1 0 Requests use HTTP 1 1 but responses must be in HTTP 1 0 MSIE 4 0b2 has this problem Its Java VM makes requests in HTTP 1 1 format but the responses must be in HTTP 1 0 format in particular it does not understand chunked responses The workaround is to fool Apache into believing the request came in HTTP 1 0 format BrowserMatch MSIE 4 0b2 downgrade 1 0 force response 1 0 This workaround is available in 1 2 2 and in a patch against 1 2 1 Boundary problems with header parsing All versions of Navigator from 2 0 through 4 0b2 and possibly later have a problem if the trailing CRLF of the response header starts at offset 256 257 or 258 of the response A BrowserMatch for this would match on nearly every hit so the workaround is enabled automatically on all responses The workaround implemented detects when this condition would occur in a response and adds extra padding to the header to push the trailing CRLF past offset 258 of the response Multipart responses and Quoted Boundary Strings On multipart responses some clients will not accept quotes around the boundary string The MIME standard recommends that such quotes be used But the clients were probably written based on one of the examples in RFC2068 which does not include quotes Apache does not include quotes on its boundary strings to workaround this problem Byterange Requests A byterange request is used when the client wishes to retrieve a portion of an object not necessarily the entire object There was a very old draft which included these byteranges in the URL Old clients such as Navigator 2 0b1 and MSIE 3 0 for the MAC exhibit this behaviour and it will appear in the servers access logs as failed attempts to retrieve a URL with a trailing xxx yyy Apache does not attempt to implement this at all A subsequent draft of this standard defines a header Request Range and a response type multipart x byteranges The HTTP 1 1 standard includes this draft with a few fixes and it defines the header Range and type multipart byteranges Navigator versions 2 and 3 sends both Range and Request Range headers with the same value but does not accept a multipart byteranges response The response must be multipart x byteranges As a workaround if Apache receives a Request Range header it considers it higher priority than a Range header and in response uses multipart x byteranges The Adobe Acrobat Reader plugin makes extensive use of byteranges and prior to version 3 01 supports only the multipart x byterange response Unfortunately there is no clue that it is the plugin making the request If the plugin is

    Original URL path: http://ama09.obspm.fr/manual-2.0/misc/known_client_problems.html (2015-11-16)
    Open archived version from archive

  • Descriptors and Apache - Apache HTTP Server
    See the respective man pages for more information For example you can probably use ulimit n unlimited to raise your soft limit up to the hard limit You should include this command in a shell script which starts your webserver Unfortunately it s not always this simple As mentioned above you will probably run into some system limitations that will need to be worked around somehow Work was done in version 1 2 1 to improve the situation somewhat Here is a partial list of systems and workarounds assuming you are using 1 2 1 or later BSDI 2 0 FreeBSD 2 2 BSDI 2 1 Linux Solaris through 2 5 1 AIX SCO OpenServer Compaq Tru64 UNIX Digital UNIX OSF Others BSDI 2 0 Under BSDI 2 0 you can build Apache to support more descriptors by adding DFD SETSIZE nnn to EXTRA CFLAGS where nnn is the number of descriptors you wish to support keep it less than the hard limit But it will run into trouble if more than approximately 240 Listen directives are used This may be cured by rebuilding your kernel with a higher FD SETSIZE FreeBSD 2 2 BSDI 2 1 Similar to the BSDI 2 0 case you should define FD SETSIZE and rebuild But the extra Listen limitation doesn t exist Linux By default Linux has a kernel maximum of 256 open descriptors per process There are several patches available for the 2 0 x series which raise this to 1024 and beyond and you can find them in the unofficial patches section of the Linux Information HQ None of these patches are perfect and an entirely different approach is likely to be taken during the 2 1 x development Applying these patches will raise the FD SETSIZE used to compile all programs and unless you rebuild all your libraries you should avoid running any other program with a soft descriptor limit above 256 As of this writing the patches available for increasing the number of descriptors do not take this into account On a dedicated webserver you probably won t run into trouble Solaris through 2 5 1 Solaris has a kernel hard limit of 1024 may be lower in earlier versions But it has a limitation that files using the stdio library cannot have a descriptor above 255 Apache uses the stdio library for the ErrorLog directive When you have more than approximately 110 virtual hosts with an error log and an access log each you will need to build Apache with DHIGH SLACK LINE 256 added to EXTRA CFLAGS You will be limited to approximately 240 error logs if you do this AIX AIX version 3 2 appears to have a hard limit of 128 descriptors End of story Version 4 1 5 has a hard limit of 2000 SCO OpenServer Edit the etc conf cf d stune file or use etc conf cf d configure choice 7 User and Group configuration and modify the NOFILES kernel parameter to

    Original URL path: http://ama09.obspm.fr/manual-2.0/misc/descriptors.html (2015-11-16)
    Open archived version from archive



  •