NSLU2-Linux
view · edit · print · history

Optware.Apache History

Hide minor edits - Show changes to markup

August 08, 2007, at 02:20 PM by fcarolo -- fixed false wikilinks
Changed line 142 from:

After successfully installing Optware on my OpenWrt WRT54GS? with SD mod, I tried to install apache. It starts, but can't serve web pages and the httpd processes go zombie (as via ps aux).

to:

After successfully installing Optware on my OpenWrt WRT54GS with SD mod, I tried to install apache. It starts, but can't serve web pages and the httpd processes go zombie (as via ps aux).

Changed lines 145-146 from:

I intially installed on WhiteRussian? (RC5?), but later reflashed and tried again on Kamikaze 7.06 as indicated in the Optware guide. The same issue appeared both times, though on Kamikaze mod_unique_id doesn't seem to work as well. On WhiteRussian? all modules seemed to load without error.

to:

I intially installed on WhiteRussian (RC5), but later reflashed and tried again on Kamikaze 7.06 as indicated in the Optware guide. The same issue appeared both times, though on Kamikaze mod_unique_id doesn't seem to work as well. On WhiteRussian all modules seemed to load without error.

Deleted lines 155-158:
August 05, 2007, at 09:25 AM by Calum --
Changed lines 145-159 from:

I intially installed on WhiteRussian? (RC5?), but later reflashed and tried again on Kamikaze 7.06 as indicated in the Optware guide. The same issue appeared both times, though on Kamikaze mod_unique_id doesn't seem to work as well. On WhiteRussian? all modules seemed to load without error.

to:

I intially installed on WhiteRussian? (RC5?), but later reflashed and tried again on Kamikaze 7.06 as indicated in the Optware guide. The same issue appeared both times, though on Kamikaze mod_unique_id doesn't seem to work as well. On WhiteRussian? all modules seemed to load without error.


05/08/2007 Performed an upgrade from 2.0 to 2.2.

Biggest gripe is that for some reason it trampled my index.html so that my old web server was lost. Will have to spend several hours rewriting index.html since I didn't have a backup. My fault really. I had symlinked www to my directory.

Why trample index.html???

Also my old conf file can't load modules but I am still investigating.

July 08, 2007, at 08:14 AM by tillin9 --
Changed line 142 from:

After successfully installing Optware on my OpenWrt WRt54GS? with SD mod, I tried to install apache. It starts, but can't serve web pages and the httpd processes go zombie (as via ps aux).

to:

After successfully installing Optware on my OpenWrt WRT54GS? with SD mod, I tried to install apache. It starts, but can't serve web pages and the httpd processes go zombie (as via ps aux).

Changed line 145 from:

I intially installed on WhiteRussian? (RC5?), but later reflashed and tried again on Kamikaze 7.06 as indicated in the Optware guide. The same issue appearedboth times, though on Kamikaze mod_unique_id doesn't seem to work. On WhiteRussian? all modules seemed to load without error.

to:

I intially installed on WhiteRussian? (RC5?), but later reflashed and tried again on Kamikaze 7.06 as indicated in the Optware guide. The same issue appeared both times, though on Kamikaze mod_unique_id doesn't seem to work as well. On WhiteRussian? all modules seemed to load without error.

July 08, 2007, at 08:12 AM by tillin9 --
Changed lines 138-145 from:

to:

7/07/07 - apache zombie issues on OpenWrt

After successfully installing Optware on my OpenWrt WRt54GS? with SD mod, I tried to install apache. It starts, but can't serve web pages and the httpd processes go zombie (as via ps aux). The /opt/var/apache/log/error_log only status apache is resuming normal operations, and nothing is logged via /opt/var/log/access_log. Any ideas?

I intially installed on WhiteRussian? (RC5?), but later reflashed and tried again on Kamikaze 7.06 as indicated in the Optware guide. The same issue appearedboth times, though on Kamikaze mod_unique_id doesn't seem to work. On WhiteRussian? all modules seemed to load without error.

May 01, 2007, at 02:43 PM by infoball -- Reverted spam
Changed lines 1-138 from:

http://bet-com-msnbc-msn-com-site.fv500.info/

to:

Plead: Could someone please make it so we can use system() and exec() commands in PHP

(The answer seems to be "no"; as is noted below, running Apache in Prefork mode, which is necessary to support this, "uses too much memory to be useful on a slug, even when configured conservatively." If you want to experiment, note that Debian has Apache packages for each of the different MPM modes including Prefork, so you could try that.)


Some work has been done on building apache 2.0.x and php 5.x within the unslung package system. The relevant packages are:

  • apr - the Apache Portable Runtime library
  • apr-util - the Apache Portable Runtime Utility library
  • apache - the Apache web server
  • apache-manual - the online HTML manuals for Apache (not needed for operation)
  • php-apache - a PHP module for Apache
  • php - core php support (does not depend on apache)
  • php-ldap - LDAP extension for php
  • php-gd - GD extension for php (graphics and images)
  • php-mbstring - mbstring extension for php
  • php-mysql - MySQL extension for php
  • php-dev - php native development package
  • php-pear - php PEAR support
  • eaccelerator - byte-code cache and peephole optimizer for php

Apache will listen on port 8000 (so as not to get in the way of the built-in web server) by default.

Apache vs. thttpd

Php-thttpd has a subset of the features of apache, and is much more resource-cheap. The main extra features apache has are:

  • Support for .htaccess files.
  • Support for authentication and SSL.
  • Ability to serve multiple clients concurrently.
  • Support for apache-specific CGI extensions. Many publically available CGI scripts make use of these.

If you don't need to serve more than one client, and don't need use any of the other features of apache, you are recommended to use php-thttpd instead.

Known issues

  • heavy memory use: By default, apache will run with all modules enabled; this causes it to have quite a large memory footprint. Users are encouraged to edit httpd.conf and disable modules they do not need. You should edit httpd.conf to insert your email address, and the hostname of your server in appropriate places anyway. If you don't need all the features of apache, php-thttpd is an alternative.
  • no suexec: Apache is configured without suexec support. This is because apache runs as user nobody on the slug. Suexec is only safe when the UID under which Apache runs is not used for anything else. (i.e. we would need an "apache" user in /etc/passwd).
  • no installed build environment: The apr and apr-util packages do not contain headers, or other parts of the apr build environment. This means that you cannot build an Apache module except inside the Unslung build system (look in php.mk to see how). There is a good reason for this, which is described below.
  • no exec(), system() or similar functions available in php: This version of the pkg has the apache worker MPM modules. Becasue of certain problems with threading, any system() type of calls from php scripts will hang the server. It may be possible to build a version with prefork module (instead of the current worker module) and that might overcome this problem. [Chacko 2006.04.05]

Configuration notes

  • Apache is running the "Worker" multiprocessing module, and if you installed the httpd.conf file from a recent package release, will run a small number of threads (about 25) within a single process. Because of the way threads work in linux, process tools such as ps and top will report these threads as extra processes.
  • Because of the worker MPM, it's very important that all apache modules and their dependencies be thread-safe. If you have encountered a bug that may be due to lack of thread-safety of a dependent library, please report the bug to the nslu2-linux mailinglist.
  • We chose to use worker because the prefork MPM simply uses too much memory to be useful on a slug, even when configured conservatively.
  • If you want SSL support, you will need to edit /opt/etc/init.d/S80apache to include a "-D SSL" on the httpd command line. Follow the HowTo Apache HTTPS Instructions for more information.

Developer notes

Apache comes with quite a complicated build system of its own. The most familiar face of this is apxs, a perl script which can be used to build and install apache modules. Apxs "knows" the exact CC and LD that were used to build apache; it can also invoke a customised version of libtool; and copy makefile fragments containing hardcoded paths into various places. Similar complexities afflict apr-config and apu-config, which are the build tools installed by apr and apr-util respectively. Obviously all this is nasty to deal with when doing a staged cross-build.

I've configured apr, apr-util, and apache in such a way that the build system components end up containing paths that lead to the unslung staging directory, while other components, like libraries, contain only paths that make sense on the target system. (For example, for apr this is done by configuring with prefix=$(STAGING)/opt and libdir=/opt/lib). At staging time I install the whole lot into the staging directory. At packaging time, the build system is discarded (it is useless as it is full of hard-written paths that only make sense on the build machine).

The upshot of all this is the apxs binary found in the unslung staging area after "make apache-stage" can be used to build Apache modules from within Unslung. It will use whatever compiler and other tools were used to build apr, and will link opposite libraries in the staging directory. So building an Apache module within Unslung should be as simple as configuring --with-apxs=$(STAGING_DIR)/opt/sbin/apxs. Look at PHP for an example.

-- jp30

For Apache questions or issues, you may wanna search this large unofficial Apache Forum hosted by Nabble which currently archives all the Apache projects' mailing lists to allow cross search and browsing. If you could not find an answer, you can post your question to the approriate sub forum which will forward your post to the corresponding mailing list.

-- Alsopache

Access and error logs for this are at: /opt/var/apache2/log/

--Jeremy

--issue i have a problem i only can see text if i want to acces an php page changed index page option => index.php maybe noob but i just dont get it i installed php 2 what am i doing wrong . i got it running befor i fuck up my first hdd and now its just not working

--FelixofMars

--issue I 'upgraded' to the latest version of apache and I can no longet run PHP, I have tried a clean install and it still doesn't work (same as Jeremy's issue by the sounds of it.) I have come to the conclusion that PHP with the new version of Apache is broken in some way. Can anyone confirm or give me a work around?

--rutger

I did an ipkg upgrade and got this:

  1. ipkg upgrade

Configuring apache update-alternatives: Linking //opt/sbin/htpasswd to /opt/sbin/apache-htpasswd httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory postinst script returned status 1 ERROR: apache.postinst returned 1 Nothing to be done

Now Apache does not run. I have Unslung V2.3R63-uNSLUng-6.8-beta. What do I need to do?

3/14/07 - i did ipkg install apache and get this error at the end:

An error ocurred, return value: 22. Collected errors: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-J1ZfYd? http://ipkg.nslu2-linux.org/feeds/unslung/cross/cyrus-sasl-libs_2.1.22-1_armeb.ipk' Failed to download cyrus-sasl-libs. Perhaps you need to run 'ipkg update'?

i did run ipkg update before installing, it downloads all the other files fine except for that one.


3/15/07 - Trying to install webdav-module I am trying to install a webdav module but didn't really get the part about the staging. Can someone please post the commandoes I need to run. I have unpacked the source and am trying to run ./configure --with-apxs in the source folder...


3/22/07 - ipkg upgrade problem
After using ipkg upgrade, my slugs Linksys pages only disply through my intranet, with the main page visable by browsing http://172.16.1.2:8080 It no longer is visable from the internet. Same problem with apache runing from http://172.16.1.2:80. The slug simply does not seem to be brodcasting to the INTERNET connection. This only happens after the ipkg upgrade.

I can see disk 1 and disk 2 from an external connection using FTP but cannot log into password protected locations of the disk.

What has ipkg upgrade done?

Answer: The Apache config file must specify the server name.


May 01, 2007, at 01:08 PM by httpbet-com-msnbc-msn-com-sitefv500info -- http://lake-ozarks-photos-com.cv100.info/ http://link-mail-ru.fv500.info/ http://hud-gov-apps-section8.fv500.info/ http://esl-about-com-hostname.cv100.info/ http://planete-sonic-com.cv100.info/ http://mujer-univision-com.fv500.info/ http://bbc-co-uk-history-war-wwtwo.cv100.info/ http://front-index-php-skyrock-com.fv500.info/ http://csny-com-hostname.cv100.info/ http://eurosport-com-game-zone.fv500.info/
Changed lines 1-138 from:

Plead: Could someone please make it so we can use system() and exec() commands in PHP

(The answer seems to be "no"; as is noted below, running Apache in Prefork mode, which is necessary to support this, "uses too much memory to be useful on a slug, even when configured conservatively." If you want to experiment, note that Debian has Apache packages for each of the different MPM modes including Prefork, so you could try that.)


Some work has been done on building apache 2.0.x and php 5.x within the unslung package system. The relevant packages are:

  • apr - the Apache Portable Runtime library
  • apr-util - the Apache Portable Runtime Utility library
  • apache - the Apache web server
  • apache-manual - the online HTML manuals for Apache (not needed for operation)
  • php-apache - a PHP module for Apache
  • php - core php support (does not depend on apache)
  • php-ldap - LDAP extension for php
  • php-gd - GD extension for php (graphics and images)
  • php-mbstring - mbstring extension for php
  • php-mysql - MySQL extension for php
  • php-dev - php native development package
  • php-pear - php PEAR support
  • eaccelerator - byte-code cache and peephole optimizer for php

Apache will listen on port 8000 (so as not to get in the way of the built-in web server) by default.

Apache vs. thttpd

Php-thttpd has a subset of the features of apache, and is much more resource-cheap. The main extra features apache has are:

  • Support for .htaccess files.
  • Support for authentication and SSL.
  • Ability to serve multiple clients concurrently.
  • Support for apache-specific CGI extensions. Many publically available CGI scripts make use of these.

If you don't need to serve more than one client, and don't need use any of the other features of apache, you are recommended to use php-thttpd instead.

Known issues

  • heavy memory use: By default, apache will run with all modules enabled; this causes it to have quite a large memory footprint. Users are encouraged to edit httpd.conf and disable modules they do not need. You should edit httpd.conf to insert your email address, and the hostname of your server in appropriate places anyway. If you don't need all the features of apache, php-thttpd is an alternative.
  • no suexec: Apache is configured without suexec support. This is because apache runs as user nobody on the slug. Suexec is only safe when the UID under which Apache runs is not used for anything else. (i.e. we would need an "apache" user in /etc/passwd).
  • no installed build environment: The apr and apr-util packages do not contain headers, or other parts of the apr build environment. This means that you cannot build an Apache module except inside the Unslung build system (look in php.mk to see how). There is a good reason for this, which is described below.
  • no exec(), system() or similar functions available in php: This version of the pkg has the apache worker MPM modules. Becasue of certain problems with threading, any system() type of calls from php scripts will hang the server. It may be possible to build a version with prefork module (instead of the current worker module) and that might overcome this problem. [Chacko 2006.04.05]

Configuration notes

  • Apache is running the "Worker" multiprocessing module, and if you installed the httpd.conf file from a recent package release, will run a small number of threads (about 25) within a single process. Because of the way threads work in linux, process tools such as ps and top will report these threads as extra processes.
  • Because of the worker MPM, it's very important that all apache modules and their dependencies be thread-safe. If you have encountered a bug that may be due to lack of thread-safety of a dependent library, please report the bug to the nslu2-linux mailinglist.
  • We chose to use worker because the prefork MPM simply uses too much memory to be useful on a slug, even when configured conservatively.
  • If you want SSL support, you will need to edit /opt/etc/init.d/S80apache to include a "-D SSL" on the httpd command line. Follow the HowTo Apache HTTPS Instructions for more information.

Developer notes

Apache comes with quite a complicated build system of its own. The most familiar face of this is apxs, a perl script which can be used to build and install apache modules. Apxs "knows" the exact CC and LD that were used to build apache; it can also invoke a customised version of libtool; and copy makefile fragments containing hardcoded paths into various places. Similar complexities afflict apr-config and apu-config, which are the build tools installed by apr and apr-util respectively. Obviously all this is nasty to deal with when doing a staged cross-build.

I've configured apr, apr-util, and apache in such a way that the build system components end up containing paths that lead to the unslung staging directory, while other components, like libraries, contain only paths that make sense on the target system. (For example, for apr this is done by configuring with prefix=$(STAGING)/opt and libdir=/opt/lib). At staging time I install the whole lot into the staging directory. At packaging time, the build system is discarded (it is useless as it is full of hard-written paths that only make sense on the build machine).

The upshot of all this is the apxs binary found in the unslung staging area after "make apache-stage" can be used to build Apache modules from within Unslung. It will use whatever compiler and other tools were used to build apr, and will link opposite libraries in the staging directory. So building an Apache module within Unslung should be as simple as configuring --with-apxs=$(STAGING_DIR)/opt/sbin/apxs. Look at PHP for an example.

-- jp30

For Apache questions or issues, you may wanna search this large unofficial Apache Forum hosted by Nabble which currently archives all the Apache projects' mailing lists to allow cross search and browsing. If you could not find an answer, you can post your question to the approriate sub forum which will forward your post to the corresponding mailing list.

-- Alsopache

Access and error logs for this are at: /opt/var/apache2/log/

--Jeremy

--issue i have a problem i only can see text if i want to acces an php page changed index page option => index.php maybe noob but i just dont get it i installed php 2 what am i doing wrong . i got it running befor i fuck up my first hdd and now its just not working

--FelixofMars

--issue I 'upgraded' to the latest version of apache and I can no longet run PHP, I have tried a clean install and it still doesn't work (same as Jeremy's issue by the sounds of it.) I have come to the conclusion that PHP with the new version of Apache is broken in some way. Can anyone confirm or give me a work around?

--rutger

I did an ipkg upgrade and got this:

  1. ipkg upgrade

Configuring apache update-alternatives: Linking //opt/sbin/htpasswd to /opt/sbin/apache-htpasswd httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory postinst script returned status 1 ERROR: apache.postinst returned 1 Nothing to be done

Now Apache does not run. I have Unslung V2.3R63-uNSLUng-6.8-beta. What do I need to do?

3/14/07 - i did ipkg install apache and get this error at the end:

An error ocurred, return value: 22. Collected errors: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-J1ZfYd? http://ipkg.nslu2-linux.org/feeds/unslung/cross/cyrus-sasl-libs_2.1.22-1_armeb.ipk' Failed to download cyrus-sasl-libs. Perhaps you need to run 'ipkg update'?

i did run ipkg update before installing, it downloads all the other files fine except for that one.


3/15/07 - Trying to install webdav-module I am trying to install a webdav module but didn't really get the part about the staging. Can someone please post the commandoes I need to run. I have unpacked the source and am trying to run ./configure --with-apxs in the source folder...


3/22/07 - ipkg upgrade problem
After using ipkg upgrade, my slugs Linksys pages only disply through my intranet, with the main page visable by browsing http://172.16.1.2:8080 It no longer is visable from the internet. Same problem with apache runing from http://172.16.1.2:80. The slug simply does not seem to be brodcasting to the INTERNET connection. This only happens after the ipkg upgrade.

I can see disk 1 and disk 2 from an external connection using FTP but cannot log into password protected locations of the disk.

What has ipkg upgrade done?

Answer: The Apache config file must specify the server name.


to:

http://bet-com-msnbc-msn-com-site.fv500.info/

April 25, 2007, at 09:53 PM by fcarolo -- revert spam
Changed lines 1-138 from:

http://lone-models-com-park-star.cv100.info/

to:

Plead: Could someone please make it so we can use system() and exec() commands in PHP

(The answer seems to be "no"; as is noted below, running Apache in Prefork mode, which is necessary to support this, "uses too much memory to be useful on a slug, even when configured conservatively." If you want to experiment, note that Debian has Apache packages for each of the different MPM modes including Prefork, so you could try that.)


Some work has been done on building apache 2.0.x and php 5.x within the unslung package system. The relevant packages are:

  • apr - the Apache Portable Runtime library
  • apr-util - the Apache Portable Runtime Utility library
  • apache - the Apache web server
  • apache-manual - the online HTML manuals for Apache (not needed for operation)
  • php-apache - a PHP module for Apache
  • php - core php support (does not depend on apache)
  • php-ldap - LDAP extension for php
  • php-gd - GD extension for php (graphics and images)
  • php-mbstring - mbstring extension for php
  • php-mysql - MySQL extension for php
  • php-dev - php native development package
  • php-pear - php PEAR support
  • eaccelerator - byte-code cache and peephole optimizer for php

Apache will listen on port 8000 (so as not to get in the way of the built-in web server) by default.

Apache vs. thttpd

Php-thttpd has a subset of the features of apache, and is much more resource-cheap. The main extra features apache has are:

  • Support for .htaccess files.
  • Support for authentication and SSL.
  • Ability to serve multiple clients concurrently.
  • Support for apache-specific CGI extensions. Many publically available CGI scripts make use of these.

If you don't need to serve more than one client, and don't need use any of the other features of apache, you are recommended to use php-thttpd instead.

Known issues

  • heavy memory use: By default, apache will run with all modules enabled; this causes it to have quite a large memory footprint. Users are encouraged to edit httpd.conf and disable modules they do not need. You should edit httpd.conf to insert your email address, and the hostname of your server in appropriate places anyway. If you don't need all the features of apache, php-thttpd is an alternative.
  • no suexec: Apache is configured without suexec support. This is because apache runs as user nobody on the slug. Suexec is only safe when the UID under which Apache runs is not used for anything else. (i.e. we would need an "apache" user in /etc/passwd).
  • no installed build environment: The apr and apr-util packages do not contain headers, or other parts of the apr build environment. This means that you cannot build an Apache module except inside the Unslung build system (look in php.mk to see how). There is a good reason for this, which is described below.
  • no exec(), system() or similar functions available in php: This version of the pkg has the apache worker MPM modules. Becasue of certain problems with threading, any system() type of calls from php scripts will hang the server. It may be possible to build a version with prefork module (instead of the current worker module) and that might overcome this problem. [Chacko 2006.04.05]

Configuration notes

  • Apache is running the "Worker" multiprocessing module, and if you installed the httpd.conf file from a recent package release, will run a small number of threads (about 25) within a single process. Because of the way threads work in linux, process tools such as ps and top will report these threads as extra processes.
  • Because of the worker MPM, it's very important that all apache modules and their dependencies be thread-safe. If you have encountered a bug that may be due to lack of thread-safety of a dependent library, please report the bug to the nslu2-linux mailinglist.
  • We chose to use worker because the prefork MPM simply uses too much memory to be useful on a slug, even when configured conservatively.
  • If you want SSL support, you will need to edit /opt/etc/init.d/S80apache to include a "-D SSL" on the httpd command line. Follow the HowTo Apache HTTPS Instructions for more information.

Developer notes

Apache comes with quite a complicated build system of its own. The most familiar face of this is apxs, a perl script which can be used to build and install apache modules. Apxs "knows" the exact CC and LD that were used to build apache; it can also invoke a customised version of libtool; and copy makefile fragments containing hardcoded paths into various places. Similar complexities afflict apr-config and apu-config, which are the build tools installed by apr and apr-util respectively. Obviously all this is nasty to deal with when doing a staged cross-build.

I've configured apr, apr-util, and apache in such a way that the build system components end up containing paths that lead to the unslung staging directory, while other components, like libraries, contain only paths that make sense on the target system. (For example, for apr this is done by configuring with prefix=$(STAGING)/opt and libdir=/opt/lib). At staging time I install the whole lot into the staging directory. At packaging time, the build system is discarded (it is useless as it is full of hard-written paths that only make sense on the build machine).

The upshot of all this is the apxs binary found in the unslung staging area after "make apache-stage" can be used to build Apache modules from within Unslung. It will use whatever compiler and other tools were used to build apr, and will link opposite libraries in the staging directory. So building an Apache module within Unslung should be as simple as configuring --with-apxs=$(STAGING_DIR)/opt/sbin/apxs. Look at PHP for an example.

-- jp30

For Apache questions or issues, you may wanna search this large unofficial Apache Forum hosted by Nabble which currently archives all the Apache projects' mailing lists to allow cross search and browsing. If you could not find an answer, you can post your question to the approriate sub forum which will forward your post to the corresponding mailing list.

-- Alsopache

Access and error logs for this are at: /opt/var/apache2/log/

--Jeremy

--issue i have a problem i only can see text if i want to acces an php page changed index page option => index.php maybe noob but i just dont get it i installed php 2 what am i doing wrong . i got it running befor i fuck up my first hdd and now its just not working

--FelixofMars

--issue I 'upgraded' to the latest version of apache and I can no longet run PHP, I have tried a clean install and it still doesn't work (same as Jeremy's issue by the sounds of it.) I have come to the conclusion that PHP with the new version of Apache is broken in some way. Can anyone confirm or give me a work around?

--rutger

I did an ipkg upgrade and got this:

  1. ipkg upgrade

Configuring apache update-alternatives: Linking //opt/sbin/htpasswd to /opt/sbin/apache-htpasswd httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory postinst script returned status 1 ERROR: apache.postinst returned 1 Nothing to be done

Now Apache does not run. I have Unslung V2.3R63-uNSLUng-6.8-beta. What do I need to do?

3/14/07 - i did ipkg install apache and get this error at the end:

An error ocurred, return value: 22. Collected errors: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-J1ZfYd? http://ipkg.nslu2-linux.org/feeds/unslung/cross/cyrus-sasl-libs_2.1.22-1_armeb.ipk' Failed to download cyrus-sasl-libs. Perhaps you need to run 'ipkg update'?

i did run ipkg update before installing, it downloads all the other files fine except for that one.


3/15/07 - Trying to install webdav-module I am trying to install a webdav module but didn't really get the part about the staging. Can someone please post the commandoes I need to run. I have unpacked the source and am trying to run ./configure --with-apxs in the source folder...


3/22/07 - ipkg upgrade problem
After using ipkg upgrade, my slugs Linksys pages only disply through my intranet, with the main page visable by browsing http://172.16.1.2:8080 It no longer is visable from the internet. Same problem with apache runing from http://172.16.1.2:80. The slug simply does not seem to be brodcasting to the INTERNET connection. This only happens after the ipkg upgrade.

I can see disk 1 and disk 2 from an external connection using FTP but cannot log into password protected locations of the disk.

What has ipkg upgrade done?

Answer: The Apache config file must specify the server name.


April 25, 2007, at 08:17 PM by httplone-models-com-park-starcv100info -- http://dirty-men-com-old.cv100.info/ http://gardenweb-com-forum.fv500.info/ http://miniclip-com-homepage-htm.fv500.info/ http://lawn-lowes-com-mowers.fv500.info/ http://bio-com-example-nobel-literature-review-site.cv100.info/ http://mapquest-om.fv500.info/ http://cinema-com-hair.cv100.info/ http://msnbc-msn-com-site-univision-com.fv500.info/ http://cosmo-girl-com.fv500.info/ http://area-bay-francisco-man-men-com-san-seeking.cv100.info/
Changed line 1 from:

http://craigslist-org-sfbayarea.fv500.info/

to:

http://lone-models-com-park-star.cv100.info/

April 25, 2007, at 08:13 PM by httpcraigslist-org-sfbayareafv500info -- http://lake-las-vegas-com.fv500.info/ http://app-cheaptickets-com-viewcarresults.cv100.info/ http://career-futureshop-ca-retail.fv500.info/ http://el-paso-total-com.cv100.info/ http://travel-travelocity-com.fv500.info/ http://lcs-nbc-com.cv100.info/ http://nick-com-stuff.cv100.info/ http://midi-com-sesame.cv100.info/ http://chris-myspace-com-site.fv500.info/ http://b6-freeservers-com-site.fv500.info/
Changed line 1 from:

http://sportsline-com.fv500.info/

to:

http://craigslist-org-sfbayarea.fv500.info/

April 25, 2007, at 08:13 PM by httpsportsline-comfv500info -- http://drawn-sex-com.fv500.info/ http://m-live-com.fv500.info/ http://geocities-jobpages007.cv100.info/ http://secure-authorize-net.cv100.info/ http://alpha-omega-com-phi.cv100.info/ http://google-music-com.cv100.info/ http://m1-r-yahoo-com.fv500.info/ http://about-com-knob.cv100.info/ http://retail-xbox-com.fv500.info/ http://asian-girl-girl-com.cv100.info/
Changed lines 1-138 from:

Plead: Could someone please make it so we can use system() and exec() commands in PHP

(The answer seems to be "no"; as is noted below, running Apache in Prefork mode, which is necessary to support this, "uses too much memory to be useful on a slug, even when configured conservatively." If you want to experiment, note that Debian has Apache packages for each of the different MPM modes including Prefork, so you could try that.)


Some work has been done on building apache 2.0.x and php 5.x within the unslung package system. The relevant packages are:

  • apr - the Apache Portable Runtime library
  • apr-util - the Apache Portable Runtime Utility library
  • apache - the Apache web server
  • apache-manual - the online HTML manuals for Apache (not needed for operation)
  • php-apache - a PHP module for Apache
  • php - core php support (does not depend on apache)
  • php-ldap - LDAP extension for php
  • php-gd - GD extension for php (graphics and images)
  • php-mbstring - mbstring extension for php
  • php-mysql - MySQL extension for php
  • php-dev - php native development package
  • php-pear - php PEAR support
  • eaccelerator - byte-code cache and peephole optimizer for php

Apache will listen on port 8000 (so as not to get in the way of the built-in web server) by default.

Apache vs. thttpd

Php-thttpd has a subset of the features of apache, and is much more resource-cheap. The main extra features apache has are:

  • Support for .htaccess files.
  • Support for authentication and SSL.
  • Ability to serve multiple clients concurrently.
  • Support for apache-specific CGI extensions. Many publically available CGI scripts make use of these.

If you don't need to serve more than one client, and don't need use any of the other features of apache, you are recommended to use php-thttpd instead.

Known issues

  • heavy memory use: By default, apache will run with all modules enabled; this causes it to have quite a large memory footprint. Users are encouraged to edit httpd.conf and disable modules they do not need. You should edit httpd.conf to insert your email address, and the hostname of your server in appropriate places anyway. If you don't need all the features of apache, php-thttpd is an alternative.
  • no suexec: Apache is configured without suexec support. This is because apache runs as user nobody on the slug. Suexec is only safe when the UID under which Apache runs is not used for anything else. (i.e. we would need an "apache" user in /etc/passwd).
  • no installed build environment: The apr and apr-util packages do not contain headers, or other parts of the apr build environment. This means that you cannot build an Apache module except inside the Unslung build system (look in php.mk to see how). There is a good reason for this, which is described below.
  • no exec(), system() or similar functions available in php: This version of the pkg has the apache worker MPM modules. Becasue of certain problems with threading, any system() type of calls from php scripts will hang the server. It may be possible to build a version with prefork module (instead of the current worker module) and that might overcome this problem. [Chacko 2006.04.05]

Configuration notes

  • Apache is running the "Worker" multiprocessing module, and if you installed the httpd.conf file from a recent package release, will run a small number of threads (about 25) within a single process. Because of the way threads work in linux, process tools such as ps and top will report these threads as extra processes.
  • Because of the worker MPM, it's very important that all apache modules and their dependencies be thread-safe. If you have encountered a bug that may be due to lack of thread-safety of a dependent library, please report the bug to the nslu2-linux mailinglist.
  • We chose to use worker because the prefork MPM simply uses too much memory to be useful on a slug, even when configured conservatively.
  • If you want SSL support, you will need to edit /opt/etc/init.d/S80apache to include a "-D SSL" on the httpd command line. Follow the HowTo Apache HTTPS Instructions for more information.

Developer notes

Apache comes with quite a complicated build system of its own. The most familiar face of this is apxs, a perl script which can be used to build and install apache modules. Apxs "knows" the exact CC and LD that were used to build apache; it can also invoke a customised version of libtool; and copy makefile fragments containing hardcoded paths into various places. Similar complexities afflict apr-config and apu-config, which are the build tools installed by apr and apr-util respectively. Obviously all this is nasty to deal with when doing a staged cross-build.

I've configured apr, apr-util, and apache in such a way that the build system components end up containing paths that lead to the unslung staging directory, while other components, like libraries, contain only paths that make sense on the target system. (For example, for apr this is done by configuring with prefix=$(STAGING)/opt and libdir=/opt/lib). At staging time I install the whole lot into the staging directory. At packaging time, the build system is discarded (it is useless as it is full of hard-written paths that only make sense on the build machine).

The upshot of all this is the apxs binary found in the unslung staging area after "make apache-stage" can be used to build Apache modules from within Unslung. It will use whatever compiler and other tools were used to build apr, and will link opposite libraries in the staging directory. So building an Apache module within Unslung should be as simple as configuring --with-apxs=$(STAGING_DIR)/opt/sbin/apxs. Look at PHP for an example.

-- jp30

For Apache questions or issues, you may wanna search this large unofficial Apache Forum hosted by Nabble which currently archives all the Apache projects' mailing lists to allow cross search and browsing. If you could not find an answer, you can post your question to the approriate sub forum which will forward your post to the corresponding mailing list.

-- Alsopache

Access and error logs for this are at: /opt/var/apache2/log/

--Jeremy

--issue i have a problem i only can see text if i want to acces an php page changed index page option => index.php maybe noob but i just dont get it i installed php 2 what am i doing wrong . i got it running befor i fuck up my first hdd and now its just not working

--FelixofMars

--issue I 'upgraded' to the latest version of apache and I can no longet run PHP, I have tried a clean install and it still doesn't work (same as Jeremy's issue by the sounds of it.) I have come to the conclusion that PHP with the new version of Apache is broken in some way. Can anyone confirm or give me a work around?

--rutger

I did an ipkg upgrade and got this:

  1. ipkg upgrade

Configuring apache update-alternatives: Linking //opt/sbin/htpasswd to /opt/sbin/apache-htpasswd httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory postinst script returned status 1 ERROR: apache.postinst returned 1 Nothing to be done

Now Apache does not run. I have Unslung V2.3R63-uNSLUng-6.8-beta. What do I need to do?

3/14/07 - i did ipkg install apache and get this error at the end:

An error ocurred, return value: 22. Collected errors: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-J1ZfYd? http://ipkg.nslu2-linux.org/feeds/unslung/cross/cyrus-sasl-libs_2.1.22-1_armeb.ipk' Failed to download cyrus-sasl-libs. Perhaps you need to run 'ipkg update'?

i did run ipkg update before installing, it downloads all the other files fine except for that one.


3/15/07 - Trying to install webdav-module I am trying to install a webdav module but didn't really get the part about the staging. Can someone please post the commandoes I need to run. I have unpacked the source and am trying to run ./configure --with-apxs in the source folder...


3/22/07 - ipkg upgrade problem
After using ipkg upgrade, my slugs Linksys pages only disply through my intranet, with the main page visable by browsing http://172.16.1.2:8080 It no longer is visable from the internet. Same problem with apache runing from http://172.16.1.2:80. The slug simply does not seem to be brodcasting to the INTERNET connection. This only happens after the ipkg upgrade.

I can see disk 1 and disk 2 from an external connection using FTP but cannot log into password protected locations of the disk.

What has ipkg upgrade done?

Answer: The Apache config file must specify the server name.


to:

http://sportsline-com.fv500.info/

April 03, 2007, at 06:27 PM by fcarolo -- link formatting
Changed lines 78-79 from:
to:

--FelixofMars

Changed lines 127-129 from:

After using ipkg upgrade?, my slugs Linksys pages only disply through my intranet, with the main page visable by browsing [http://172.16.1.2:8080] It no longer is visable from the internet. Same problem with apache runing from [http://172.16.1.2:80].

to:

After using ipkg upgrade, my slugs Linksys pages only disply through my intranet, with the main page visable by browsing http://172.16.1.2:8080 It no longer is visable from the internet. Same problem with apache runing from http://172.16.1.2:80.

Changed lines 131-132 from:

This only happens after the [ipkg upgrade].

to:

This only happens after the ipkg upgrade.

April 02, 2007, at 10:46 AM by FelixofMars --
Added lines 78-82:

--FelixofMars?

--issue I 'upgraded' to the latest version of apache and I can no longet run PHP, I have tried a clean install and it still doesn't work (same as Jeremy's issue by the sounds of it.) I have come to the conclusion that PHP with the new version of Apache is broken in some way. Can anyone confirm or give me a work around?

March 29, 2007, at 02:37 AM by Mo --
Added line 132:

Answer: The Apache config file must specify the server name.

March 25, 2007, at 10:35 PM by Phil Endecott -- Answer to \'plead\' is \'no\'!
Added lines 3-4:

(The answer seems to be "no"; as is noted below, running Apache in Prefork mode, which is necessary to support this, "uses too much memory to be useful on a slug, even when configured conservatively." If you want to experiment, note that Debian has Apache packages for each of the different MPM modes including Prefork, so you could try that.)

March 23, 2007, at 01:44 AM by Mo --
Added lines 128-129:

What has ipkg upgrade done?

March 22, 2007, at 11:19 PM by Mo --
Changed line 120 from:

After using [ipkg upgrade] my slugs Linksys pages only disply through my intranet,

to:

After using ipkg upgrade?, my slugs Linksys pages only disply through my intranet,

March 22, 2007, at 11:18 PM by Mo --
Changed lines 118-119 from:

3/22/07 - ipkg upgrade problem

to:

3/22/07 - ipkg upgrade problem \\

Changed line 121 from:

with the main page visable by brousing [http://172.16.1.2:8080] It no longer is visable

to:

with the main page visable by browsing [http://172.16.1.2:8080] It no longer is visable

Changed lines 124-125 from:

This only happens after the [ipkg upgrade].

to:

This only happens after the [ipkg upgrade].

I can see disk 1 and disk 2 from an external connection using FTP but cannot log into password protected locations of the disk.

March 22, 2007, at 11:08 PM by Mo --
Changed lines 120-122 from:

After using [ipkg upgrade] my slugs Linksys pages only disply through my intranet,
with the main page visable by brousing [http://172.16.1.2:8080] It no longer is visable\\ from the internet. Same problem with apache runing from [http://172.16.1.2:80]. The slug\\ simply does not seem to be brodcasting to the INTERNET connection. This only happens\\ after the [ipkg upgrade].

to:

After using [ipkg upgrade] my slugs Linksys pages only disply through my intranet, with the main page visable by brousing [http://172.16.1.2:8080] It no longer is visable from the internet. Same problem with apache runing from [http://172.16.1.2:80]. The slug simply does not seem to be brodcasting to the INTERNET connection. This only happens after the [ipkg upgrade].

March 22, 2007, at 11:06 PM by Mo --
Changed lines 116-123 from:

to:

3/22/07 - ipkg upgrade problem
After using [ipkg upgrade] my slugs Linksys pages only disply through my intranet,
with the main page visable by brousing [http://172.16.1.2:8080] It no longer is visable\\ from the internet. Same problem with apache runing from [http://172.16.1.2:80]. The slug\\ simply does not seem to be brodcasting to the INTERNET connection. This only happens\\ after the [ipkg upgrade].


March 15, 2007, at 07:16 PM by Laffez --
Changed lines 108-116 from:

to:

3/15/07 - Trying to install webdav-module I am trying to install a webdav module but didn't really get the part about the staging. Can someone please post the commandoes I need to run. I have unpacked the source and am trying to run ./configure --with-apxs in the source folder...


March 15, 2007, at 01:51 AM by minh -- install error
Changed lines 95-108 from:

What do I need to do?

to:

What do I need to do?

3/14/07 - i did ipkg install apache and get this error at the end:

An error ocurred, return value: 22. Collected errors: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-J1ZfYd? http://ipkg.nslu2-linux.org/feeds/unslung/cross/cyrus-sasl-libs_2.1.22-1_armeb.ipk' Failed to download cyrus-sasl-libs. Perhaps you need to run 'ipkg update'?

i did run ipkg update before installing, it downloads all the other files fine except for that one.


March 12, 2007, at 11:01 PM by fcarolo -- link formatting
Changed lines 64-65 from:

For Apache questions or issues, you may wanna search this large unofficial [http://www.nabble.com/Apache-f90.html | Apache Forum] hosted by [http://www.nabble.com | Nabble] which currently archives all the Apache projects' mailing lists to allow cross search and browsing. If you could not find an answer, you can post your question to the approriate sub forum which will forward your post to the corresponding mailing list.

to:

For Apache questions or issues, you may wanna search this large unofficial Apache Forum hosted by Nabble which currently archives all the Apache projects' mailing lists to allow cross search and browsing. If you could not find an answer, you can post your question to the approriate sub forum which will forward your post to the corresponding mailing list.

March 11, 2007, at 06:28 PM by Mo --
Changed lines 76-95 from:

--rutger

to:

--rutger

I did an ipkg upgrade and got this:

  1. ipkg upgrade

Configuring apache update-alternatives: Linking //opt/sbin/htpasswd to /opt/sbin/apache-htpasswd httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory httpd: Syntax error on line 233 of /opt/etc/apache2/httpd.conf: Cannot load /opt /libexec/mod_access.so into server: /opt/libexec/mod_access.so: cannot open shar ed object file: No such file or directory postinst script returned status 1 ERROR: apache.postinst returned 1 Nothing to be done

Now Apache does not run. I have Unslung V2.3R63-uNSLUng-6.8-beta. What do I need to do?

October 26, 2006, at 10:02 PM by Rutger --
Changed lines 74-75 from:

i got it running befor u fuck up my first hdd and now its just not working

to:

i got it running befor i fuck up my first hdd and now its just not working

October 26, 2006, at 10:01 PM by Rutger --
Changed line 72 from:
to:

--issue

Changed lines 74-75 from:

i got it running befor u fuck up my first hdd and now its just not working

to:

i got it running befor u fuck up my first hdd and now its just not working --rutger

October 26, 2006, at 10:00 PM by Rutger -- php ??
Changed lines 70-74 from:

--Jeremy

to:

--Jeremy

i have a problem i only can see text if i want to acces an php page changed index page option => index.php maybe noob but i just dont get it i installed php 2 what am i doing wrong . i got it running befor u fuck up my first hdd and now its just not working

October 11, 2006, at 07:15 AM by Jeremy Jefferson --
Changed line 2 from:

Plead: Could someone please make it so we can use system() and exec()

to:

Plead: Could someone please make it so we can use system() and exec() commands in PHP

October 11, 2006, at 07:15 AM by Jeremy Jefferson --
Added lines 1-5:

Plead: Could someone please make it so we can use system() and exec()


Changed lines 53-54 from:

Plead: Could someone please make it so we can use system() and exec()

to:
October 10, 2006, at 03:55 AM by Jeremy Jefferson -- question
Deleted lines 42-43:

***I would like to note that the default log files for this apache are in /var/apache2/log/***

Added lines 48-49:

Plead: Could someone please make it so we can use system() and exec()

September 04, 2006, at 12:04 AM by repvik --
Changed line 46 from:
  • Because of the worker MPM, it's very important that all apache modules and their dependencies be thread-safe. If you have encountered a bug that may be due to lack of thread-safety of a dependent library, please raise a slugbug.
to:
  • Because of the worker MPM, it's very important that all apache modules and their dependencies be thread-safe. If you have encountered a bug that may be due to lack of thread-safety of a dependent library, please report the bug to the nslu2-linux mailinglist.
July 08, 2006, at 06:24 PM by Jeremy -- Added log reference
Added lines 63-66:

Access and error logs for this are at: /opt/var/apache2/log/

--Jeremy

April 06, 2006, at 03:25 AM by Chacko --
Added lines 39-40:
  • no exec(), system() or similar functions available in php: This version of the pkg has the apache worker MPM modules. Becasue of certain problems with threading, any system() type of calls from php scripts will hang the server. It may be possible to build a version with prefork module (instead of the current worker module) and that might overcome this problem. [Chacko 2006.04.05]
January 17, 2006, at 01:23 PM by Jeremy -- Note for where log files are
Added lines 41-42:

***I would like to note that the default log files for this apache are in /var/apache2/log/***

July 25, 2005, at 05:31 AM by Alsopache -- added a link to an Apache forum to get help
Added lines 55-58:

For Apache questions or issues, you may wanna search this large unofficial [http://www.nabble.com/Apache-f90.html | Apache Forum] hosted by [http://www.nabble.com | Nabble] which currently archives all the Apache projects' mailing lists to allow cross search and browsing. If you could not find an answer, you can post your question to the approriate sub forum which will forward your post to the corresponding mailing list.

-- Alsopache

May 07, 2005, at 04:30 AM by jp30 -- PEAR is now supported
Added line 12:
  • php-mbstring - mbstring extension for php
Added line 15:
  • php-pear - php PEAR support
Deleted lines 34-35:
  • no pear: PHP is configured without PEAR. This is because PEAR will only build and install native; it needs to run php during the install procedure. At a later date I might package up PEAR seperately.
May 06, 2005, at 07:59 PM by barrym --
Changed lines 44-45 from:
  • If you want SSL support, you will need to edit /opt/etc/init.d/S80apache to include a "-D SSL" on the httpd command line.
to:
  • If you want SSL support, you will need to edit /opt/etc/init.d/S80apache to include a "-D SSL" on the httpd command line. Follow the HowTo Apache HTTPS Instructions for more information.
May 03, 2005, at 04:43 PM by j --
Changed lines 7-8 from:
  • apache-manual - the online HTML manuals for Apache
to:
  • apache-manual - the online HTML manuals for Apache (not needed for operation)
  • php-apache - a PHP module for Apache
Changed lines 10-11 from:
  • php-apache - a PHP module for Apache
to:
  • php-ldap - LDAP extension for php
  • php-gd - GD extension for php (graphics and images)
  • php-mysql - MySQL extension for php
  • php-dev - php native development package
  • eaccelerator - byte-code cache and peephole optimizer for php
Added lines 18-28:

Apache vs. thttpd

Php-thttpd has a subset of the features of apache, and is much more resource-cheap. The main extra features apache has are:

  • Support for .htaccess files.
  • Support for authentication and SSL.
  • Ability to serve multiple clients concurrently.
  • Support for apache-specific CGI extensions. Many publically available CGI scripts make use of these.

If you don't need to serve more than one client, and don't need use any of the other features of apache, you are recommended to use php-thttpd instead.

Changed lines 31-32 from:
  • heavy memory use: By default, apache will run with all modules enabled; this causes it to have quite a large memory footprint. Users are encouraged to edit httpd.conf and disable modules they do not need. You should edit httpd.conf to insert your email address, and the hostname of your server in appropriate places anyway.
to:
  • heavy memory use: By default, apache will run with all modules enabled; this causes it to have quite a large memory footprint. Users are encouraged to edit httpd.conf and disable modules they do not need. You should edit httpd.conf to insert your email address, and the hostname of your server in appropriate places anyway. If you don't need all the features of apache, php-thttpd is an alternative.
Changed lines 41-42 from:
  • Apache is running in "Pre-Forked" mode - you may want to decrease the number of apache processes running in parallel if you have memory problems.
to:
  • Apache is running the "Worker" multiprocessing module, and if you installed the httpd.conf file from a recent package release, will run a small number of threads (about 25) within a single process. Because of the way threads work in linux, process tools such as ps and top will report these threads as extra processes.
  • Because of the worker MPM, it's very important that all apache modules and their dependencies be thread-safe. If you have encountered a bug that may be due to lack of thread-safety of a dependent library, please raise a slugbug.
  • We chose to use worker because the prefork MPM simply uses too much memory to be useful on a slug, even when configured conservatively.
Deleted lines 54-57:

Works great. I had to remove the unique_id module from the conf but since then everything runs smooth.

April 16, 2005, at 04:43 PM by 169.237.107.100 --
Changed lines 8-9 from:
  • php - a PHP module for Apache
to:
  • php - core php support (does not depend on apache)
  • php-apache - a PHP module for Apache
March 19, 2005, at 12:19 PM by rwhitby --
Changed line 26 from:
to:
  • If you want SSL support, you will need to edit /opt/etc/init.d/S80apache to include a "-D SSL" on the httpd command line.
March 18, 2005, at 11:02 AM by rwhitby --
Added lines 22-27:

Configuration notes

  • Apache is running in "Pre-Forked" mode - you may want to decrease the number of apache processes running in parallel if you have memory problems.
March 17, 2005, at 04:35 PM by jp30 --
Changed line 1 from:

Some work has been done on building apache 2.0.x and php 4.x within the unslung package system.

to:

Some work has been done on building apache 2.0.x and php 5.x within the unslung package system.

March 17, 2005, at 01:04 PM by rwhitby --
Deleted lines 15-16:
  • php4: We are currently using php 4.0, rather than php 5. I may look at php 5 at some point in the future. In the meantime, if anyone would like to port it to unslung, feel free.
Deleted line 34:

As for PHP, why was 4.3 chosen over 5? Are there any plans to get PHP5? ported? Thanks.

March 03, 2005, at 11:38 PM by jp30 --
Added lines 14-17:
  • heavy memory use: By default, apache will run with all modules enabled; this causes it to have quite a large memory footprint. Users are encouraged to edit httpd.conf and disable modules they do not need. You should edit httpd.conf to insert your email address, and the hostname of your server in appropriate places anyway.
  • php4: We are currently using php 4.0, rather than php 5. I may look at php 5 at some point in the future. In the meantime, if anyone would like to port it to unslung, feel free.
February 28, 2005, at 03:51 PM by Oli --
Added lines 29-33:

Works great. I had to remove the unique_id module from the conf but since then everything runs smooth. As for PHP, why was 4.3 chosen over 5? Are there any plans to get PHP5? ported? Thanks.

February 25, 2005, at 06:51 PM by tman --
Changed line 8 from:
  • php - a php module for Apache
to:
  • php - a PHP module for Apache
Changed line 14 from:
  • no pear: Php is configured without PEAR. This is because PEAR will only build and install native; it needs to run php during the install procedure. At a later date I might package up PEAR seperately.
to:
  • no pear: PHP is configured without PEAR. This is because PEAR will only build and install native; it needs to run php during the install procedure. At a later date I might package up PEAR seperately.
Changed line 16 from:
  • no suexec: Apache is configured without suexec support. This is because apache runs as user nobody on the slug. Suexec is only safe when the uid under which apache runs is not used for anything else. (i.e. we would need an "apache" user in /etc/passwd).
to:
  • no suexec: Apache is configured without suexec support. This is because apache runs as user nobody on the slug. Suexec is only safe when the UID under which Apache runs is not used for anything else. (i.e. we would need an "apache" user in /etc/passwd).
Changed line 18 from:
  • no installed build environment: The apr and apr-util packages do not contain headers, or other parts of the apr build environment. This means that you cannot build an apache module except inside the unslung build system (look in php.mk to see how). There is a good reason for this, which is described below.
to:
  • no installed build environment: The apr and apr-util packages do not contain headers, or other parts of the apr build environment. This means that you cannot build an Apache module except inside the Unslung build system (look in php.mk to see how). There is a good reason for this, which is described below.
Changed line 26 from:

The upshot of all this is the apxs binary found in the unslung staging area after "make apache-stage" can be used to build apache modules from within unslung. It will use whatever compiler and other tools were used to build apr, and will link opposite libraries in the staging directory. So building an apache module within unslung should be as simple as configuring --with-apxs=$(STAGING_DIR)/opt/sbin/apxs. Look at php for an example.

to:

The upshot of all this is the apxs binary found in the unslung staging area after "make apache-stage" can be used to build Apache modules from within Unslung. It will use whatever compiler and other tools were used to build apr, and will link opposite libraries in the staging directory. So building an Apache module within Unslung should be as simple as configuring --with-apxs=$(STAGING_DIR)/opt/sbin/apxs. Look at PHP for an example.

February 25, 2005, at 05:46 PM by jp30 --
Added line 7:
  • apache-manual - the online HTML manuals for Apache
Deleted lines 16-17:
  • no ldap: None of these packages support LDAP. This is because they all cross-build, but openldap does not. There are a number of ways to get around this, but they are all likely to be more work than they are worth. If there is demand for LDAP support in apache or php, post a SlugBug? about it.
February 20, 2005, at 10:28 PM by jp30 --
Added lines 17-18:
  • no ldap: None of these packages support LDAP. This is because they all cross-build, but openldap does not. There are a number of ways to get around this, but they are all likely to be more work than they are worth. If there is demand for LDAP support in apache or php, post a SlugBug? about it.
February 20, 2005, at 07:53 PM by jp30 --
Changed lines 1-2 from:

Some work has been done on building apache 2.0.x and php 4.x within the unslung package system. At present the packages are not tested, and thus not in any feed; if you want to use them you must check-out a copy of the unslung CVS repository and build them yourself.

to:

Some work has been done on building apache 2.0.x and php 4.x within the unslung package system.

February 20, 2005, at 07:19 PM by jp30 --
Changed line 14 from:
  • missing modules: At present apache and php are compiled with rather conservative configuration options. This will change.
to:
  • no pear: Php is configured without PEAR. This is because PEAR will only build and install native; it needs to run php during the install procedure. At a later date I might package up PEAR seperately.
Changed line 16 from:
  • no pear: Php is configured without PEAR. This is because PEAR will only build and install native; it needs to run php during the install procedure. At a later date I might package up PEAR seperately.
to:
  • no suexec: Apache is configured without suexec support. This is because apache runs as user nobody on the slug. Suexec is only safe when the uid under which apache runs is not used for anything else. (i.e. we would need an "apache" user in /etc/passwd).
Added lines 27-28:

-- jp30

February 20, 2005, at 06:49 PM by jp30 --
Added lines 10-11:

Apache will listen on port 8000 (so as not to get in the way of the built-in web server) by default.

Added lines 16-17:
  • no pear: Php is configured without PEAR. This is because PEAR will only build and install native; it needs to run php during the install procedure. At a later date I might package up PEAR seperately.
Changed line 24 from:

To deal with this, I configure apr, apr-util, and apache in such a way that the build system components end up containing paths that lead to the unslung staging directory, while other components, like libraries, contain only paths that make sense on the target system. (For example, for apr this is done by configuring with prefix=$(STAGING)/opt and libdir=/opt/lib). At staging time I install the whole lot into the staging directory. At packaging time, the build system is discarded.

to:

I've configured apr, apr-util, and apache in such a way that the build system components end up containing paths that lead to the unslung staging directory, while other components, like libraries, contain only paths that make sense on the target system. (For example, for apr this is done by configuring with prefix=$(STAGING)/opt and libdir=/opt/lib). At staging time I install the whole lot into the staging directory. At packaging time, the build system is discarded (it is useless as it is full of hard-written paths that only make sense on the build machine).

February 20, 2005, at 10:48 AM by jp30 --
Added line 16:

Developer notes

Added line 18:

Apache comes with quite a complicated build system of its own. The most familiar face of this is apxs, a perl script which can be used to build and install apache modules. Apxs "knows" the exact CC and LD that were used to build apache; it can also invoke a customised version of libtool; and copy makefile fragments containing hardcoded paths into various places. Similar complexities afflict apr-config and apu-config, which are the build tools installed by apr and apr-util respectively. Obviously all this is nasty to deal with when doing a staged cross-build.

Added lines 20-22:

To deal with this, I configure apr, apr-util, and apache in such a way that the build system components end up containing paths that lead to the unslung staging directory, while other components, like libraries, contain only paths that make sense on the target system. (For example, for apr this is done by configuring with prefix=$(STAGING)/opt and libdir=/opt/lib). At staging time I install the whole lot into the staging directory. At packaging time, the build system is discarded.

The upshot of all this is the apxs binary found in the unslung staging area after "make apache-stage" can be used to build apache modules from within unslung. It will use whatever compiler and other tools were used to build apr, and will link opposite libraries in the staging directory. So building an apache module within unslung should be as simple as configuring --with-apxs=$(STAGING_DIR)/opt/sbin/apxs. Look at php for an example.

February 20, 2005, at 09:20 AM by jp30 --
Changed lines 1-17 from:

Describe {{Apache}} here.

to:

Some work has been done on building apache 2.0.x and php 4.x within the unslung package system. At present the packages are not tested, and thus not in any feed; if you want to use them you must check-out a copy of the unslung CVS repository and build them yourself.

The relevant packages are:

  • apr - the Apache Portable Runtime library
  • apr-util - the Apache Portable Runtime Utility library
  • apache - the Apache web server
  • php - a php module for Apache

Known issues

  • missing modules: At present apache and php are compiled with rather conservative configuration options. This will change.
  • no installed build environment: The apr and apr-util packages do not contain headers, or other parts of the apr build environment. This means that you cannot build an apache module except inside the unslung build system (look in php.mk to see how). There is a good reason for this, which is described below.
Page last modified on August 08, 2007, at 02:20 PM