cvs commit: apache-1.3/src/support apxs.8
rse 98/12/18 02:53:22 Modified:src CHANGES src/support apxs.8 Log: Update APXS manual page: some -q option arguments were missing and another was incorrect. Submitted by: Mark Anderson <[EMAIL PROTECTED]> Reviewed by: Ralf S. Engelschall PR: 3553 Revision ChangesPath 1.1174+3 -0 apache-1.3/src/CHANGES Index: CHANGES === RCS file: /home/cvs/apache-1.3/src/CHANGES,v retrieving revision 1.1173 retrieving revision 1.1174 diff -u -r1.1173 -r1.1174 --- CHANGES 1998/12/17 15:09:27 1.1173 +++ CHANGES 1998/12/18 10:53:20 1.1174 @@ -1,5 +1,8 @@ Changes with Apache 1.3.4 + *) Update APXS manual page: some -q option arguments were missing + and another was incorrect. [Mark Anderson <[EMAIL PROTECTED]>] PR#3553 + *) Cleanup the command line options: `-?' was documented to show the usage list but does it with an error because `?' is not a valid command. OTOH a lot of users expect `-h' to print such a usage list and 1.4 +6 -5 apache-1.3/src/support/apxs.8 Index: apxs.8 === RCS file: /home/cvs/apache-1.3/src/support/apxs.8,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- apxs.81998/12/02 09:52:18 1.3 +++ apxs.81998/12/18 10:53:21 1.4 @@ -205,11 +205,12 @@ .I query parameters can be one or more of the following strings: .nf - CC PREFIX - LD SBINDIR - CFLAGS INCLUDEDIR - CFLAGS_SHLIB LIBEXECDIR - LDFLAGS_SHLIB SYSCONFDIR + CC TARGET + CFLAGS SBINDIR + CFLAGS_SHLIBINCLUDEDIR + LD_SHLIBLIBEXECDIR + LDFLAGS_SHLIB SYSCONFDIR + LIBS_SHLIB .fi Use this for manually determining settings. For instance use .nf
cvs commit: apache-site/contributors index.html
dgaudet 98/12/18 10:05:24 Modified:contributors index.html Log: I've changed jobs Revision ChangesPath 1.55 +3 -6 apache-site/contributors/index.html Index: index.html === RCS file: /home/cvs/apache-site/contributors/index.html,v retrieving revision 1.54 retrieving revision 1.55 diff -u -r1.54 -r1.55 --- index.html1998/11/19 15:57:52 1.54 +++ index.html1998/12/18 18:05:23 1.55 @@ -255,19 +255,16 @@ Email: [EMAIL PROTECTED] URL: http://www.arctic.org/~dgaudet/";>http://www.arctic.org/~dgaudet/ -Organization: http://www.transmeta.com/";>Transmeta Corporation +Organization: http://www.cp.net/";>Critical Path -Occupation: Performance Analyst +Occupation: Sr. Software Engineer Location: San Francisco, CA, USA Comments: Performance freak. OS Expertise: Linux Contributions: Performance/reliability coding, and general bug fixes. Believes in the One True Tab Width of 8 columns. Known to be a hard-nosed - pain in the butt. -In a previous life Dean worked at - http://www.hotwired.com/";>HotWired, which is where - he started hacking Apache. + pain in the butt. Name: Matthew Gray
cvs commit: apache-site/contributors index.html
coar98/12/18 10:37:10 Modified:contributors index.html Log: Add 'em if you've got 'em.. Revision ChangesPath 1.56 +8 -5 apache-site/contributors/index.html Index: index.html === RCS file: /home/cvs/apache-site/contributors/index.html,v retrieving revision 1.55 retrieving revision 1.56 diff -u -r1.55 -r1.56 --- index.html1998/12/18 18:05:23 1.55 +++ index.html1998/12/18 18:37:09 1.56 @@ -163,6 +163,7 @@ development mailing list. +http://Web.Golux.Com/coar/pix/coar.gif"; ALIGN=RIGHT ALT="[photo]"> Name: Ken Coar Email: mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] URL: http://Web.Golux.Com/coar/";>http://Web.Golux.Com/coar/ @@ -171,15 +172,16 @@ Location: Research Triangle Park, North Carolina, USA Comments: HTML pedant, FAQ editor, UI perfectionist, bugdb script hacker -OS Expertise: Digital UNIX, OpenVMS +OS Expertise: Digital UNIX, OpenVMS, Linux (RedHat) Contributions: The 1.2 example API module, moderately updated FAQ, mod_autoindex enhancements, various minor bug fixes and documentation corrections. Eminently capable of writing code that will Rule The World by consuming resources - but in an elegant way. - + + Name: Mark Cox email: mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] URL: http://www.awe.com/~mark/";>http://www.awe.com/~mark/ @@ -341,7 +343,7 @@ Comments: What am I doing here? - +http://www.lerdorf.on.ca/rasmus.jpg"; ALIGN=RIGHT ALT="[photo]"> Name: Rasmus Lerdorf Email: mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] URL: http://www.lerdorf.on.ca/";>http://www.lerdorf.on.ca/ @@ -349,8 +351,9 @@ Occupation: IT Consultant Location: Toronto, Ontario, Canada OS Expertise: Solaris, Linux -Contribution: Wrote mod_info module included in the distribution, as well - as mod_php which is available separately. +Contribution: Wrote mod_info module included in the + distribution, as well as mod_php which is available separately. +
cvs commit: apache-1.3/htdocs/manual/misc perf-tuning.html
dgaudet 98/12/18 14:29:57 Modified:htdocs/manual/misc perf-tuning.html Log: file moved Revision ChangesPath 1.16 +1 -1 apache-1.3/htdocs/manual/misc/perf-tuning.html Index: perf-tuning.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/perf-tuning.html,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- perf-tuning.html 1998/12/13 20:42:16 1.15 +++ perf-tuning.html 1998/12/18 22:29:56 1.16 @@ -340,7 +340,7 @@ implement a mutual exclusion semaphore. Only one child can have the mutex at any time. There are several choices for implementing these mutexes. The choice is defined in src/conf.h (pre-1.3) or -src/main/conf.h (1.3 or later). Some architectures +src/include/ap_config.h (1.3 or later). Some architectures do not have any locking choice made, on these architectures it is unsafe to use multiple Listen directives.
cvs commit: apache-1.3/htdocs/manual/vhosts name-based.html
lars98/12/18 15:49:45 Modified:htdocs/manual/vhosts name-based.html Log: Some updates/modifications (based on the patch from the PR). PR: 3549 Submitted by: Joshua Slive <[EMAIL PROTECTED]> Revision ChangesPath 1.9 +30 -15apache-1.3/htdocs/manual/vhosts/name-based.html Index: name-based.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/vhosts/name-based.html,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- name-based.html 1998/09/17 12:33:12 1.8 +++ name-based.html 1998/12/18 23:49:44 1.9 @@ -40,34 +40,49 @@ Using non-IP Virtual Hosts Using the new virtual hosts is quite easy, and superficially looks -like the old method. You simply add to one of the Apache configuration -files (most likely httpd.conf or srm.conf) -code similar to the following: +like the old method. The notable difference between IP-based and +name-based virtual host configuration is the +NameVirtualHost +directive which specifies an IP address that should be used as a +target for name-based virtual hosts. + +For example, suppose that both www.domain.tld and +www.otherdomain.tld point at the IP address +111.22.33.44. Then you simply add to one of the Apache +configuration files (most likely httpd.conf or +srm.conf) code similar to the following: + + + NameVirtualHost 111.22.33.44ServerName www.domain.tld -DocumentRoot /web/domain +DocumentRoot /www/domain - -The notable difference between IP-based and name-based virtual host -configuration is the -NameVirtualHost -directive which specifies an IP address that should be used as a target for -name-based virtual hosts. ++ServerName www.otherdomain.tld +DocumentRoot /www/otherdomain + + Of course, any additional directives can (and should) be placed into thesection. To make this work, -all that is needed is to make sure that the name -www.domain.tld points to the IP address -111.22.33.44 +all that is needed is to make sure that the names +www.domain.tld and www.otherdomain.tld +are pointing to the IP address 111.22.33.44 Note: When you specify an IP address in a NameVirtualHost directive then requests to that IP address will only ever be served -by matching s. The "main server" will never -be served from the specified IP address. +by matching s. The "main server" will +never be served from the specified IP address. +If you start to use virtual hosts you should stop to use the "main server" +as an independent server and rather use it as a place for +configuration directives that are common for all your virtual hosts. +In other words, you should add a section for +every server (hostname) you want to maintain on your server. Additionally, many servers may wish to be accessible by more than one name. For example, the example server might want to be accessible
