Uploaded image for project: 'JBoss Core Services'
  1. JBoss Core Services
  2. JBCS-185

Solaris: Apachectl do not set ServerRoot - bundled httpd.conf is not loaded

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • httpd 2.4.23 ER2
    • httpd 2.4.23 DR3
    • httpd
    • None
    • ER2

      When apachectl is executed on 2.4.23-DR3, the process arguments are:

      argv[0]: /opt/hudson/jbcs-httpd24-2.4/sbin/httpd
      argv[1]: -k
      argv[2]: start
      

      And 2.4.6 arguments looks like:

      argv[0]: /opt/hudson/jbcs-httpd24-2.4/sbin/httpd
      argv[1]: -d
      argv[2]: /opt/hudson/jbcs-httpd24-2.4/etc/httpd
      argv[3]: -k
      argv[4]: start
      

      This is because differences in apachectl - OPTIONS var missing:

      # 2.4.6 apachectl
      start|stop|graceful-stop)
          $HTTPD $ROOTDIR $OPTIONS -k $ARGV
      

      and

      # 2.4.23-DR3 apachectl
      start|stop|restart|graceful|graceful-stop)
          $HTTPD $ROOTDIR -k $ARGV
      

      This causes that any module config files created in conf.d are not started, because bundled httpd.conf is not loaded.

      IncludeOptional conf.d/*.conf
      

              gzaronik@redhat.com George Zaronikas
              fgoldefu@redhat.com Filip Goldefus (Inactive)
              Jan Štefl Jan Štefl
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: