It is currently Wed, 22 Mar 2023 06:02:36 GMT

Author Message
 Apache howto?
I just installed FreeBSD 4.2 on a box that is going to be (hopefully) my
webserver.  I didn't put much on it, just used the "user" option.  I've
grabbed the 1.3.19.tar.Z from a local apache mirror.  I've looked at the
install instructions, but I need a bit more hand holding (first time
FreeBSD user) than the apache docs provide.  Is there a good HOWTO on
the subject?  I've not really seen many HOWTOs at all for FreeBSD, I'm
starting to think it's just a Linux thing.

Thanks in advance,

 Thu, 11 Sep 2003 12:43:47 GMT   
 Apache howto?
Apache is not a FreeBSD thing, so if there is a Linux Apache HOWTO,
almost everything it says will also apply to FreeBSD.

Also, the book "Apache: The Definitive Guide" published by
O'Reilly may be what you want:

Stephen Montgomery-Smith

 Thu, 11 Sep 2003 23:19:13 GMT   
 Apache howto?
What I meant is that I haven't seen any HOWTOs for FreeBSD at all.  Not
just for Apache.  Thanks for the input...I'll look for the book when I go
to Borders next time.


 Fri, 12 Sep 2003 04:45:53 GMT   
 Apache howto?
Here ya go, I just installed Apache on a new Freebsd 4.2 box. Took only
about 5 mins. Needs more configuring, but it works.


  Like all good things, there are two ways to configure, compile, and
  Apache.  You can go for the 3-minute installation process using the APACI
  process described below; or, you can opt for the same mechanism used in
  previous versions of Apache, as described in the file 'src/INSTALL'.  Each
  mechanism has its benefits and drawbacks - APACI is newer and a little
  raw, but it gets you up and running the least amount of time, whereas the
  "Configuration.tmpl" mechanism may be more familiar and give you some more
  flexibility to the power user.  We'd be very interested in your comments
  feedback regarding each approach.

  Installing the Apache 1.3 HTTP server with APACI

  1. Overview for the impatient

     $ ./configure --prefix=PREFIX
     $ make
     $ make install
     $ PREFIX/bin/apachectl start

     NOTE: PREFIX is not the string "PREFIX". Instead use the Unix
           filesystem path under which Apache should be installed. For
           instance use "/usr/local/apache" for PREFIX above.

  2. Requirements

     The following requirements exist for building Apache:

     o  Disk Space:

        Make sure you have approximately 12 MB of temporary free disk space
        available.  After installation Apache occupies approximately 3 MB of
        disk space (the actual required disk space depends on the amount of
        compiled in third party modules, etc).

     o  ANSI-C Compiler:

        Make sure you have an ANSI-C compiler installed. The GNU C compiler
        (GCC) from the Free Software Foundation (FSF) is recommended
        2.7.2 is fine). If you don't have GCC then at least make sure your
        vendors compiler is ANSI compliant. You can find the homepage of GNU
        at and the GCC distribution under .

     o  Perl 5 Interpreter [OPTIONAL]:

        For some of the support scripts like `apxs' or `dbmmanage' (which
        written in Perl) the Perl 5 interpreter is required (versions 5.003
        and 5.004 are fine). If no such interpreter is found by APACI's
        `configure' script this is no harm.  Of course, you still can build
        and install Apache 1.3. Only those support scripts cannot be used.
        you have multiple Perl interpreters installed (perhaps a Perl 4 from
        the vendor and a Perl 5 from your own), then it is recommended to
        the --with-perl option (see below) to make sure the correct one is
        selected by APACI.

     o  Dynamic Shared Object (DSO) support [OPTIONAL]:

        To provide maximum flexibility Apache now is able to load modules
        under runtime via the DSO mechanism by using the pragmatic
        dlopen()/dlsym() system calls. These system calls are not available
        under all operating systems therefore you cannot use the DSO
        on all platforms. And Apache currently has only limited built-in
        knowledge on how to compile shared objects because this is heavily
        platform-dependent. The current state is this:

        o Out-of-the-box supported platforms are:
           - Linux     - SunOS         - UnixWare     - Darwin/Mac OS
           - FreeBSD   - Solaris       - AIX          - OpenStep/Mach
           - OpenBSD   - IRIX          - SCO          - DYNIX/ptx
           - NetBSD    - HPUX          - ReliantUNIX
           - BSDI      - Digital Unix  - DGUX

        o Entirely unsupported platforms are:
           - Ultrix

        If your system is not on these lists but has the dlopen-style
        interface, you either have to provide the appropriate compiler and
        linker flags (see CFLAGS_SHLIB, LDFLAGS_SHLIB and
        below) manually or at least make sure a Perl 5 interpreter is
        installed from which Apache can guess the options.

        For more in-depth information about DSO support in Apache 1.3 please
        read the document htdocs/manual/dso.html carefully. Especially the
        section entitled "Advantages & Disadvantages" because using the DSO
        mechanism can have strange side-effects if you are not carefully. BE

  3. Configuring the source tree

     NOTE: Although we'll often advise you to read the
           file parts to better understand the various options in this
           section, there is _AT NO TIME_ any need to _EDIT_ this file. The
           _COMPLETE_ configuration takes place via command line arguments
           local shell variables for the ./configure script. The
           src/Configuration.tmpl file is just a _READ-ONLY_ resource, here.


     The next step is to configure the Apache source tree for your
     platform and personal requirements. The most important setup here is
     location prefix where Apache is to be installed later, because Apache
     to be configured for this location to work correctly. But there are a
     of other options available for your pleasure.

     For a short impression of what possibilities you have, here is a
     example which compiles Apache for the installation tree /sw/pkg/apache
     with a particular compiler and flags plus the two additional modules
     mod_rewrite and mod_proxy for later loading through the DSO mechanism:

     $ CC="pgcc" OPTIM="-O2" \
       ./configure --prefix=/sw/pkg/apache \
                   --enable-module=rewrite --enable-shared=rewrite \
                   --enable-module=proxy   --enable-shared=proxy

     The complete reference of all configuration possibilities follows. For
     more real-life configuration examples please check out the file


     $ [CC=...]        [CFLAGS_SHLIB=...]           [TARGET=...]
       [OPTIM=...]     [LD_SHLIB=...]
       [CFLAGS=...]    [LDFLAGS_SHLIB=...]
       [LDFLAGS=...]   [RANLIB=...]
       [LIBS=...]      [DEPS=...]
           [--quiet]         [--prefix=DIR]            [--enable-rule=NAME]
           [--verbose]       [--exec-prefix=PREFIX]    [--disable-rule=NAME]
           [--shadow[=DIR]]  [--bindir=EPREFIX]        [--add-module=FILE]
           [--show-layout]   [--sbindir=DIR]
           [--help]          [--libexecdir=DIR]
                             [--runtimedir=DIR]        [--enable-suexec]
                             [--logfiledir=DIR]        [--suexec-caller=UID]

                             [--with-perl=FILE]        [--suexec-uidmin=UID]
                             [--without-support]       [--suexec-gidmin=GID]


     environment variables to override the corresponding default entries in
     the src/Configuration.tmpl file (see there for more information about
     their usage).

         Note: The syntax ``KEY=VALUE ./configure ...'' (one single line!)
               the GNU Autoconf compatible way of specifying defines and can
               be used with Bourne shell compatible shells only (sh, bash,
               ksh). If you use a different type of shell either use ``env
               KEY=VALUE ./configure ...'' when the `env' command is
               on your system or use ``setenv KEY VALUE; ./configure ...''
               you use one of the C-shell variants (csh, tcsh).

         Note: The above parameter names are the canonical ones used in
               Autoconf-style interfaces. But because src/Configuration.tmpl
               uses the prefix EXTRA_ for some variables (e.g. EXTRA_CFLAGS)
               these variants are accepted for backward-compatibility
               too. But please use the canonical Autoconf-style names and
               don't rely on this.

     Use the --prefix=PREFIX and --exec-prefix=EPREFIX options to configure
     Apache to use a particular installation prefix. The default is
     PREFIX=/usr/local/apache and EPREFIX=PREFIX.

     Use the --bindir=DIR, --sbindir=DIR, --libexecdir=DIR, --mandir=DIR,
     --sysconfdir=DIR, --datadir=DIR, --includedir=DIR, --localstatedir=DIR,
     --runtimedir=DIR, --logfiledir=DIR and proxycachedir=DIR option to
     the paths for particular subdirectories of the installation tree.
     Defaults are bindir=EPREFIX/bin, sbindir=EPREFIX/sbin,
     libexecdir=EPREFIX/libexec, mandir=PREFIX/man, sysconfdir=PREFIX/etc,
     datadir=PREFIX/share, includedir=PREFIX/include,
     localstatedir=PREFIX/var, runtimedir=PREFIX/var/run,
     logfiledir=PREFIX/var/log and proxycachedir=PREFIX/var/proxy.

         Note: To reduce the pollution of shared installation locations
               (like /usr/local/ or /etc) with Apache files to a minimum the
               string ``/apache'' is

read more »

 Sun, 14 Sep 2003 07:43:19 GMT   
 Apache howto?
u might want to check out some of these url's that i've put together while
researching apache as well...almost positive can't do without a book
reference unless ur familiar with Unix least thats the
best approach for a novice like myself, anyway here they are(sort of like
small hints):,5594,2604402-3,00.html

 Mon, 15 Sep 2003 23:28:21 GMT   
   [ 5 post ] 

Similar Threads

1. Apache - HowTo Set Default Page?

2. Frontpage & Apache HOWTO ???

3. Howto recompile RH/Apache

4. Apache: secure access free local, passwd external - howto?

5. Howto Change Apache Layout?

6. DBF access from Apache web server - howto

7. ANNOUNCE: Apache+SSL+PHP+frontpage Mini-Howto

8. Apache 2.0 howto write my own http-header

9. f: Howto bei einem Apache Ausfall?

10. howto in case of a breakdown apache www

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software