cvs commit: apachen/src PORTING
dgaudet 98/01/24 18:07:43 Modified:src PORTING Log: note NEED_HASHBANG_EMUL Revision ChangesPath 1.20 +4 -0 apachen/src/PORTING Index: PORTING === RCS file: /export/home/cvs/apachen/src/PORTING,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- PORTING 1998/01/23 00:36:37 1.19 +++ PORTING 1998/01/25 02:07:43 1.20 @@ -334,6 +334,10 @@ an int *len on some architectures and a size_t *len on others. If left undefined apache will default it to int. + NEED_HASHBANG_EMUL: + The execve()/etc. functions on this platform do not deal with #!, + so it must be emulated by Apache. + --- Conclusion: ---
cvs commit: apachen/src PORTING
coar97/11/16 08:12:09 Modified:src PORTING Log: Remove incorrect case on email address, and change bugdb location to the new improved one. Revision ChangesPath 1.17 +2 -2 apachen/src/PORTING Index: PORTING === RCS file: /export/home/cvs/apachen/src/PORTING,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- PORTING 1997/10/28 06:47:24 1.16 +++ PORTING 1997/11/16 16:12:09 1.17 @@ -26,8 +26,8 @@ family); the source basically uses ANSI function prototyping but no other specific ANSIisms. Thus, an ANSI-to-KR filter _may_ work, although as far as we know it has not yet been tried. If you -attempt this, let the Apache team know (send mail to [EMAIL PROTECTED] -or make a suggestion report at http://www.apache.org/bugdb.cgi). +attempt this, let the Apache team know (send mail to [EMAIL PROTECTED] +or make a suggestion report at http://bugs.apache.org/). --- The Starting Point:
cvs commit: apachen/src PORTING CHANGES
dgaudet 97/10/27 22:47:27 Modified:src PORTING CHANGES Log: Document the WANTHSREGEX change. Revision ChangesPath 1.16 +7 -2 apachen/src/PORTING Index: PORTING === RCS file: /export/home/cvs/apachen/src/PORTING,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- PORTING 1997/10/27 19:10:34 1.15 +++ PORTING 1997/10/28 06:47:24 1.16 @@ -116,8 +116,13 @@ below]) to handle OS-specific code. Each code that has and requires such OS-specific code will require a unique system cookie defined in 'CFLAGS'. You will also note that Configure also goes ahead and -predefines the LIBS and LDFLAGS Makefile variables (DEF_WANTHSREGEX is -explained below). +predefines the LIBS and LDFLAGS Makefile variables. + +DEF_WANTHSREGEX indicates the default setting of the WANTHSREGEX rule. +If left undefined it'll default to yes. Yes means the src/regex/ +directory, containing Henry Spencer's regex library will be used rather +than any system supplied regex. It's been our experience that system +supplied regex libraries are generally buggy, and to be avoided. conf.h: === 1.479 +4 -0 apachen/src/CHANGES Index: CHANGES === RCS file: /export/home/cvs/apachen/src/CHANGES,v retrieving revision 1.478 retrieving revision 1.479 diff -u -r1.478 -r1.479 --- CHANGES 1997/10/27 19:10:32 1.478 +++ CHANGES 1997/10/28 06:47:25 1.479 @@ -1,5 +1,9 @@ Changes with Apache 1.3b3 + *) PORT: All ports which don't otherwise define DEF_WANTHSREGEX will + get Spencer regex by default. This is to avoid having to + discover bugs in operating system libraries. [Dean Gaudet] + *) PORT: Fix PR#467 by generating warnings on systems which we have not been able to get working USE_*_SERIALIZED_ACCEPT settings for. Document this a bit more in src/PORTING. [Dean Gaudet] PR#467
cvs commit: apachen/src PORTING
dgaudet 97/10/24 22:34:42 Modified:src PORTING Log: typo Revision ChangesPath 1.14 +1 -1 apachen/src/PORTING Index: PORTING === RCS file: /export/home/cvs/apachen/src/PORTING,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- PORTING 1997/09/30 23:24:49 1.13 +++ PORTING 1997/10/25 05:34:41 1.14 @@ -225,7 +225,7 @@ public servers). See htdocs/manual/misc/perf-tuning.html. - USE_PTHREADS_SERIALIZED_ACCEPT: + USE_PTHREAD_SERIALIZED_ACCEPT: Use POSIX mutexes to serialize accept. See htdocs/manual/misc/perf-tuning.html.
cvs commit: apachen/src PORTING
dgaudet 97/09/30 16:24:50 Modified:src PORTING Log: document new serialization stuff Revision ChangesPath 1.13 +24 -3 apachen/src/PORTING Index: PORTING === RCS file: /export/home/cvs/apachen/src/PORTING,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- PORTING 1997/09/12 20:13:05 1.12 +++ PORTING 1997/09/30 23:24:49 1.13 @@ -205,17 +205,38 @@ USE_FCNTL_SERIALIZED_ACCEPT: Define if the OS requires a mutex lock around the socket accept() - call. Use fcntl() locking. + call. Use fcntl() locking. See htdocs/manual/misc/perf-tuning.html. USE_FLOCK_SERIALIZED_ACCEPT: Define if the OS requires a mutex lock around the socket accept() call. Use flock() locking (fcntl() is expensive on some OSs, esp. - when using NFS). + when using NFS). See htdocs/manual/misc/perf-tuning.html. + + USE_USLOCK_SERIALIZED_ACCEPT: + Probably IRIX only: use uslock() to serialize, which is far faster + on multiprocessor boxes (and far slower on uniprocessor, yay). + See htdocs/manual/misc/perf-tuning.html. + + USE_SYSVSEM_SERIALIZED_ACCEPT: + Use System V semaphores to serialize accept. These are problematic + in that they won't be cleaned up if apache is kill -9d, and there's + the potential of a CGI causing a denial of service attack if it's + running as the same uid as apache (i.e. suexec is recommended on + public servers). + See htdocs/manual/misc/perf-tuning.html. + + USE_PTHREADS_SERIALIZED_ACCEPT: + Use POSIX mutexes to serialize accept. + See htdocs/manual/misc/perf-tuning.html. + + SAFE_UNSERIALIZED_ACCEPT: + It's safe to unserialize single-socket accept(). + See htdocs/manual/misc/perf-tuning.html. USE_LONGJMP: Define to use the longjmp() call instead of siglongjmp() (as well as setjmp() instead of sigsetjmp()). - + USE_MMAP_FILES: Enable the use of mmap() for sending static files.
cvs commit: apachen/src PORTING
coar97/09/01 14:47:48 Modified:src PORTING Log: Fix some gramos and correct some email addresses that wouldn't work quite right (new-httpd is only sendable by subscribers). Revision ChangesPath 1.11 +16 -14apachen/src/PORTING Index: PORTING === RCS file: /export/home/cvs/apachen/src/PORTING,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- PORTING 1997/08/18 07:19:32 1.10 +++ PORTING 1997/09/01 21:47:46 1.11 @@ -4,12 +4,12 @@ Introduction: - Apache has been ported to a wide variety of platforms, from multiple -UNIX varients to OS/2. Starting with v1.3, it will even run under -Windows95 and NT. Nonetheless, there are most likely a few platforms -out there that currently are not officially supported under +UNIX variants to OS/2. Starting with v1.3, it will even run under +Windows95 and Windows NT. Nonetheless, there are most likely a few +platforms out there that currently are not officially supported under Apache. Porting Apache to these platforms can be quite simple -depending on the genericness of the OS. This doc will provide some -basic guidelines to help the potential porter. +depending on the genericness of the OS. This document will provide +some basic guidelines to help the potential porter. - Requirements: @@ -25,8 +25,9 @@ functions or options (eg: the %n parameter in the scanf() family); the source basically uses ANSI function prototyping but no other specific ANSIisms. Thus, an ANSI-to-KR filter _may_ -work, although as far as I know it has not yet been tried. If you -attempt this, let the Apache team know (mailto: [EMAIL PROTECTED]). +work, although as far as we know it has not yet been tried. If you +attempt this, let the Apache team know (send mail to [EMAIL PROTECTED] +or make a suggestion report at http://www.apache.org/bugdb.cgi). --- The Starting Point: @@ -52,7 +53,7 @@ If this happens to you, then it means that Configure doesn't know how to configure and compile Apache for your OS. The first course of action is the easiest: Look in Configure and see if -there are any OSs which is similar to yours. +there are any OSs which are similar to yours. For example, let's say that your OS is similar to HP-UX, but that GuessOS returns foobar-intel-hubble. You would then edit @@ -97,7 +98,7 @@ == Configure concerns itself with determining the OS-type for the build and setting up a few Makefile variables for the build. The -most important is 'OS' and 'CFLAGS'. For example, when Configure +most important are 'OS' and 'CFLAGS'. For example, when Configure determines a build for A/UX, it runs the following lines: case $PLAT in @@ -140,7 +141,7 @@ are not strictly required, but are a Good Idea anyway). The following several lines provide a list and short description -of these #defines. By correcting #defining the ones you need in conf.h +of these #defines. By correctly #defining the ones you need in conf.h (wrapped by the above mentioned system cookie), you can fine tune the build for your OS. @@ -195,7 +196,7 @@ platforms do not provide this function. If your platform does provide it _and_ it's reliable (most are not) then define this to use the OS version. Otherwise, Apache will - use it's own. + use its own. -- USE_*: @@ -212,8 +213,8 @@ when using NFS). USE_LONGJMP: - use the longjmp() call instead of siglongjmp() - (as well as setjmp() instead of sigsetjmp()) + Define to use the longjmp() call instead of siglongjmp() + (as well as setjmp() instead of sigsetjmp()). USE_MMAP_FILES: Enable the use of mmap() for sending static files. @@ -260,7 +261,8 @@ --- The above hints, and a good understanding of your OS and Apache, will go a LONG way in helping you get Apache built and running on your -OS. If you have a port, PLEASE send Email to '[EMAIL PROTECTED]' +OS. If you have a port, PLEASE send Email to '[EMAIL PROTECTED]', +or log a suggestion report at http://www.apache.org/bugdb.cgi, with the patches so that we may add them to the official version. If you hit a rough spot in the porting process, you can also try sending Email to that address as well and, if you are lucky, someone
