I just started a trial switch to Apache 2 (from ports synched as of
yesterday morning).  It's going well for the most part, but I'm finding a
few little weird things.  For example, when I first start the server, "ps"
returns a normal-looking list:

    # ps axw |grep httpd
    38308  ??  Ss     0:00.40 /usr/local/sbin/httpd -DSSL
    38309  ??  R      0:00.06 /usr/local/sbin/httpd -DSSL
    38310  ??  R      0:00.04 /usr/local/sbin/httpd -DSSL
    38311  ??  S      0:00.06 /usr/local/sbin/httpd -DSSL
    38312  ??  R      0:00.04 /usr/local/sbin/httpd -DSSL
    38313  ??  R      0:00.04 /usr/local/sbin/httpd -DSSL

Every time a guest visits a page being host with mod_perl, the name of one
of those processes gets changed to "-e" as below:

    # ps axw |grep httpd
    38308  ??  Ss     0:00.40 /usr/local/sbin/httpd -DSSL
    38309  ??  S      0:00.51 -e (httpd)
    38310  ??  S      0:00.51 -e (httpd)
    38311  ??  S      0:01.57 -e (httpd)
    38312  ??  S      0:00.50 -e (httpd)
    38313  ??  S      0:00.90 -e (httpd)
    38316  ??  S      0:00.77 -e (httpd)
    38394  p2  S+     0:00.00 grep httpd

Also, the daemons don't like to restart nicely:

    # apachectl graceful
    Syntax error on line 320 of /usr/local/etc/apache2/virtual-hosts.conf:
    Invalid command 'SSLEngine', perhaps mis-spelled or defined by a module not 
included in the server configuration

Those are the exact symptoms seen when httpd is run without the "-DSSL"
argument.  In other words, my little daemons seem to forget their name and
their arguments after they've started.  Note that despite the warning, the
daemons seem to have been successfully restarted (to the best of my

Is anyone else seeing these little peculiarities or am I the lucky one?
Kirk Strauser

"94 outdated ports on the box,
 94 outdated ports.
 Portupgrade one, an hour 'til done,
 82 outdated ports on the box."

Attachment: pgpU86N2hcJPY.pgp
Description: PGP signature

Reply via email to