passenger 4.0.30 → 4.0.31

data/build/ruby_tests.rb

@@ -29,8 +29,12 @@ task 'test:ruby' => dependencies do
 	if PlatformInfo.rspec.nil?
 		abort "RSpec is not installed for Ruby interpreter '#{PlatformInfo.ruby_command}'. Please install it."
 	else
+		if maybe_grep = string_option('E')
+			require 'shellwords'
+			maybe_grep = "-e #{Shellwords.escape(maybe_grep)}"
+		end
 		Dir.chdir("test") do
-			ruby "#{PlatformInfo.rspec} -c -f s -P 'dont-autoload-anything' ruby/*_spec.rb ruby/*/*_spec.rb"
+			ruby "#{PlatformInfo.rspec} -c -f s -P 'dont-autoload-anything' #{maybe_grep} ruby/*_spec.rb ruby/*/*_spec.rb"
 		end
 	end
 end

data/build/test_basics.rb

@@ -24,8 +24,7 @@
 TEST_BOOST_OXT_LIBRARY = LIBBOOST_OXT
 TEST_COMMON_LIBRARY    = COMMON_LIBRARY
 
-TEST_COMMON_CFLAGS = "-DTESTING_APPLICATION_POOL " <<
-	"#{EXTRA_CXXFLAGS}"
+TEST_COMMON_CFLAGS = "-DTESTING_APPLICATION_POOL #{EXTRA_CXXFLAGS}"
 
 desc "Run all unit tests and integration tests"
 task :test => ['test:oxt', 'test:cxx', 'test:ruby', 'test:node', 'test:integration']

data/debian.template/locations.ini.template

@@ -1,5 +1,6 @@
 [locations]
 natively_packaged=true
+native_packaging_method=deb
 bin_dir=/usr/bin
 agents_dir=/usr/lib/<%= PhusionPassenger::GLOBAL_NAMESPACE_DIRNAME %>/agents
 lib_dir=/usr/lib/<%= PhusionPassenger::GLOBAL_NAMESPACE_DIRNAME %>

data/debian.template/rules.template

@@ -39,7 +39,8 @@ override_dh_auto_install:
 	# Merge Ruby 1.8 and 1.9 files into a single directory.
 	cp -a pkg/fakeroot1.8/* debian/tmp/
 	cp -a pkg/fakeroot1.9.1/* debian/tmp/
-	sed -i 's|## Magic comment: set locations\.ini ##|ENV["PASSENGER_LOCATION_CONFIGURATION_FILE"] = "/usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini"|' debian/tmp/usr/bin/* debian/tmp/usr/sbin/*
+	./dev/install_scripts_bootstrap_code.rb --ruby /usr/lib/ruby/vendor_ruby debian/tmp/usr/bin/* debian/tmp/usr/sbin/*
+	./dev/install_scripts_bootstrap_code.rb --nginx-module-config /usr/bin debian/tmp/usr/share/<%= PhusionPassenger::GLOBAL_NAMESPACE_DIRNAME %>/ngx_http_passenger_module/config
 	touch debian/tmp/usr/share/<%= PhusionPassenger::GLOBAL_NAMESPACE_DIRNAME %>/release.txt
 
 override_dh_auto_clean:

data/dev/install_scripts_bootstrap_code.rb

@@ -0,0 +1,42 @@
+#!/usr/bin/env ruby
+# encoding: utf-8
+
+# This script changes the bootstrap code for all Phusion Passenger commands,
+# as well as the Nginx module config script, so that they work no
+# matter which Ruby interpreter is currently in $PATH, and no matter how
+# Phusion Passenger is packaged.
+# 
+# The bootstrap code must not add ruby_libdir to $LOAD_PATH. The active Ruby
+# can be *any* Ruby interpreter, maybe not even MRI. ruby_libdir belongs to
+# a Ruby interpreter installed by the distribution, and the files in it may
+# may be incompatible with the active Ruby.
+
+type = ARGV.shift
+
+if type == "--ruby"
+	ruby_libdir = ARGV.shift
+	BOOTSTRAP_CODE = %Q{
+		ENV["PASSENGER_LOCATION_CONFIGURATION_FILE"] = "#{ruby_libdir}/phusion_passenger/locations.ini"
+		require '#{ruby_libdir}/phusion_passenger'
+	}
+elsif type == "--nginx-module-config"
+	bindir = ARGV.shift
+	BOOTSTRAP_CODE = %Q{
+		PASSENGER_CONFIG=#{bindir}/passenger-config
+	}
+else
+	abort "Invalid type"
+end
+BOOTSTRAP_CODE.gsub!(/^\t\t/, '').strip
+
+ARGV.each do |filename|
+	File.open(filename, "r+") do |f|
+		text = f.read
+		text.sub!(
+			/^## Magic comment: begin bootstrap ##.*## Magic comment: end bootstrap \#\#$/m,
+			BOOTSTRAP_CODE)
+		f.rewind
+		f.truncate(0)
+		f.write(text)
+	end
+end

data/dev/run_travis.sh

@@ -139,6 +139,7 @@ if [[ "$TEST_DEBIAN_PACKAGING" = 1 ]]; then
 	run rake debian:dev debian:dev:reinstall
 	run rake test:integration:native_packaging \
 		LOCATIONS_INI=/usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini \
+		NATIVE_PACKAGING_METHOD=deb \
 		SUDO=1
 	run env PASSENGER_LOCATION_CONFIGURATION_FILE=/usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini \
 		rake test:integration:apache2 SUDO=1

data/dev/runner

@@ -0,0 +1,27 @@
+#!/usr/bin/env ruby
+require File.expand_path(File.dirname(__FILE__) + "/../lib/phusion_passenger")
+PhusionPassenger.locate_directories
+
+while true
+	if ARGV[0] =~ /^-r(.*)/
+		if $1.empty?
+			lib = ARGV[1]
+			ARGV.shift
+			ARGV.shift
+		else
+			lib = $1
+			ARGV.shift
+		end
+		begin
+			PhusionPassenger.require_passenger_lib(lib)
+		rescue LoadError
+			require(lib)
+		end
+	else
+		break
+	end
+end
+
+module PhusionPassenger
+	p eval(ARGV.join(" "))
+end

data/doc/Packaging.txt.md

@@ -43,8 +43,9 @@ package. This configuration comes not only with all necessary binaries, but also
 with some (but not all) source files. This is because when you run Phusion Passenger
 with a different Ruby interpreter than the packager intended, Phusion Passenger
 must be able to compile a new Ruby extension for that Ruby interpreter. This
-configuration does not however allow compiling against a different Apache or Nginx
-version than the packager intended.
+configuration does not however allow compiling against a different Apache version
+than the packager intended (but does allow compiling against a different Nginx
+version).
 
 In this configuration, files can be scattered anywhere throughout the filesystem. This
 way Phusion Passenger can be packaged in an FHS-compliant way. The exact locations
@@ -52,14 +53,8 @@ of the different types of files can be specified through a
 _location configuration file_. The existance and usage of a location configuration
 file does not automatically imply that Phusion Passenger is natively packaged.
 
-This configuration also does not allow running Phusion Passenger Standalone against
-a different Nginx version than the packager intended, but does allow running
-against a different Ruby version. Passenger Standlone looks for its binaries
-in the location as specified by the location configuration file; it makes no
-attempt to compile anything, except of course for the Ruby extension.
-
-If either the non-Standalone or the Standalone Passenger needs to have a new Ruby
-extension compiled, then it will store that in `~/.passenger/native_support/<VERSION>/<ARCH>`.
+If Phusion Passenger needs to have a new Ruby extension compiled, then it will
+store that in `~/.passenger/native_support/<VERSION>/<ARCH>`.
 
 
 # The location configuration file

data/doc/Users guide Apache.idmap.txt

@@ -338,7 +338,9 @@
 
 11.9.4. Error handling	=>	error-handling-1a1uvod
 
-11.9.5. Available hooks	=>	available-hooks-159anc3
+11.9.5. Compatibility	=>	compatibility-18tl6g3
+
+11.9.6. Available hooks	=>	available-hooks-159anc3
 
 11.10. Flying Passenger	=>	flying-passenger-q916f7
 

data/doc/Users guide Apache.txt

@@ -513,7 +513,7 @@ Please refer to link:https://github.com/phusion/passenger/wiki/Phusion-Passenger
 
 == Deploying a Meteor application
 
-Please refer to link:http://blog.phusion.nl/2013/11/01/will-meteor-kill-rails-i-dont-know-but-phusion-passenger-open-sources-meteor-support/[the Meteor tutorial].
+Please refer to link:https://github.com/phusion/passenger/wiki/Phusion-Passenger:-Meteor-tutorial[the Meteor tutorial].
 
 
 == Configuring Phusion Passenger ==
@@ -795,8 +795,8 @@ directory that's readable by Apache, but only writable by administrators.
 :version: 3.0.0
 include::users_guide_snippets/enterprise_only.txt[]
 
-Enables or disables support for rolling restarts. Normally when you
-restart an application (by touching restart.txt), Phusion Passenger would
+Enables or disables support for rolling restarts through restart.txt. Normally when you
+restart an application by touching restart.txt, Phusion Passenger would
 shut down all application processes and spawn a new one. The spawning
 of a new application process could take a while, and any requests that
 come in during this time will be blocked until this first application
@@ -822,6 +822,8 @@ Rolling restarts have a few caveat however that you should be aware of:
   been restarted. It is for this reason that you should not use rolling
   restarts in development, only in production.
 
+Please note that this option is completely unrelated to the `passenger-config restart` command. That command always initiates a blocking restart, unless `--rolling-restart` is given.
+
 This option may occur in the following places:
 
  * In the global server configuration.

data/doc/Users guide Nginx.idmap.txt

@@ -148,13 +148,15 @@
 
 8.2.9. passenger_base_uri <uri>	=>	passenger-base-uri-uri--1xtuo50
 
-8.2.10. passenger_spawn_method <string>	=>	passenger-spawn-method-string--1sc6njl
+8.2.10. passenger_document_root <path>	=>	passenger-document-root-path--1pge8kd
 
-8.2.11. passenger_load_shell_envvars <on|off>	=>	passenger-load-shell-envvars-on-off--fw5u4l
+8.2.11. passenger_spawn_method <string>	=>	passenger-spawn-method-string--1sc6njl
 
-8.2.12. passenger_rolling_restarts <on|off>	=>	passenger-rolling-restarts
+8.2.12. passenger_load_shell_envvars <on|off>	=>	passenger-load-shell-envvars-on-off--fw5u4l
 
-8.2.13. passenger_resist_deployment_errors <on|off>	=>	passenger-resist-deployment-errors-on-off--k9yf1
+8.2.13. passenger_rolling_restarts <on|off>	=>	passenger-rolling-restarts
+
+8.2.14. passenger_resist_deployment_errors <on|off>	=>	passenger-resist-deployment-errors-on-off--k9yf1
 
 8.3. Connection handling options	=>	connection-handling-options-8jgq90
 
@@ -308,7 +310,9 @@
 
 11.9.4. Error handling	=>	error-handling-m78oxs
 
-11.9.5. Available hooks	=>	available-hooks-11w1prq
+11.9.5. Compatibility	=>	compatibility-132b3ns
+
+11.9.6. Available hooks	=>	available-hooks-11w1prq
 
 11.10. Flying Passenger	=>	flying-passenger-137qg5e
 

data/doc/Users guide Nginx.txt

@@ -90,10 +90,11 @@ And you want your Rails application, located in `/websites/rails`, to be accessi
 To do this, you need to perform the following:
 
  1. Create a `location` with parameter `~ ^/<SUBURI>(/.*|$)`. This is a regular expression that says: "match everything that is exactly <SUBURI>, or starts with <SUBDURI>/".
- 2. Inside the location block, set `passenger_base_uri <SUBURI>`.
- 3. Inside the location block, set `alias <PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY>$1`.
+ 2. Inside the location block, set `alias <PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY>$1`.
+ 3. Inside the location block, set `passenger_base_uri <SUBURI>`.
  4. Inside the location block, set `passenger_app_root <PATH TO YOUR APPLICATION ROOT>`.
- 5. Inside the location block, re-specify `passenger_enabled on`.
+ 5. Inside the location block, set `passenger_document_root <PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY>`.
+ 6. Inside the location block, re-specify `passenger_enabled on`.
 
 Here is an example:
 
@@ -108,9 +109,10 @@ http {
 
         # This block has been added.
         location ~ ^/subapp(/.*|$) {
-            passenger_base_uri /subapp;
             alias /websites/rails/public$1;  # <-- be sure to point to 'public'!
+            passenger_base_uri /subapp;
             passenger_app_root /websites/rails;
+            passenger_document_root /websites/rails/public;
             passenger_enabled on;
         }
     }
@@ -281,10 +283,11 @@ And you want your Rack application, located in `/websites/rack`, to be accessibl
 To do this, you need to perform the following:
 
  1. Create a `location` with parameter `~ ^/<SUBURI>(/.*|$)`. This is a regular expression that says: "match everything that is exactly <SUBURI>, or starts with <SUBDURI>/".
- 2. Inside the location block, set `passenger_base_uri <SUBURI>`.
- 3. Inside the location block, set `alias <PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY>$1`.
+ 2. Inside the location block, set `alias <PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY>$1`.
+ 3. Inside the location block, set `passenger_base_uri <SUBURI>`.
  4. Inside the location block, set `passenger_app_root <PATH TO YOUR APPLICATION ROOT>`.
- 5. Inside the location block, re-specify `passenger_enabled on`.
+ 5. Inside the location block, set `passenger_document_root <PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY>`.
+ 6. Inside the location block, re-specify `passenger_enabled on`.
 
 Here is an example:
 
@@ -299,9 +302,10 @@ http {
 
         # This block has been added.
         location ~ ^/subapp(/.*|$) {
-            passenger_base_uri /subapp;
             alias /websites/rack/public$1;  # <-- be sure to point to 'public'!
+            passenger_base_uri /subapp;
             passenger_app_root /websites/rack;
+            passenger_document_root /websites/rack/public;
             passenger_enabled on;
         }
     }
@@ -441,10 +445,11 @@ And you want your WSGI application, located in `/websites/wsgi`, to be accessibl
 To do this, you need to perform the following:
 
  1. Create a `location` with parameter `~ ^/<SUBURI>(/.*|$)`. This is a regular expression that says: "match everything that is exactly <SUBURI>, or starts with <SUBDURI>/".
- 2. Inside the location block, set `passenger_base_uri <SUBURI>`.
- 3. Inside the location block, set `alias <PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY>$1`.
+ 2. Inside the location block, set `alias <PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY>$1`.
+ 3. Inside the location block, set `passenger_base_uri <SUBURI>`.
  4. Inside the location block, set `passenger_app_root <PATH TO YOUR APPLICATION ROOT>`.
- 5. Inside the location block, re-specify `passenger_enabled on`.
+ 5. Inside the location block, set `passenger_document_root <PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY>`.
+ 6. Inside the location block, re-specify `passenger_enabled on`.
 
 Here is an example:
 
@@ -459,9 +464,10 @@ http {
 
         # This block has been added.
         location ~ ^/subapp(/.*|$) {
-            passenger_base_uri /subapp;
             alias /websites/wsgi/public$1;  # <-- be sure to point to 'public'!
+            passenger_base_uri /subapp;
             passenger_app_root /websites/wsgi;
+            passenger_document_root /websites/wsgi/public;
             passenger_enabled on;
         }
     }
@@ -498,7 +504,7 @@ Please refer to link:https://github.com/phusion/passenger/wiki/Phusion-Passenger
 
 == Deploying a Meteor application
 
-Please refer to link:http://blog.phusion.nl/2013/11/01/will-meteor-kill-rails-i-dont-know-but-phusion-passenger-open-sources-meteor-support/[the Meteor tutorial].
+Please refer to link:https://github.com/phusion/passenger/wiki/Phusion-Passenger:-Meteor-tutorial[the Meteor tutorial].
 
 
 == Configuring Phusion Passenger ==
@@ -601,8 +607,11 @@ http {
         # If you have a web app deployed in a sub-URI, customize
         # passenger_ruby/passenger_python inside a `location` block.
         # The web app under www.bar.com/blog will use JRuby 1.7.1
-        passenger_base_uri /blog;
-        location /blog {
+        location ~ ^/blog(/.*|$) {
+            alias /websites/blog/public$1;
+            passenger_base_uri /blog;
+            passenger_app_root /websites/blog;
+            passenger_document_root /websites/blog/public;
             passenger_enabled on;
             passenger_ruby /usr/local/rvm/wrappers/jruby-1.7.1/ruby;
         }
@@ -717,6 +726,25 @@ This option may occur in the following places:
  * In a 'location' configuration block.
  * In an 'if' configuration scope.
 
+[[PassengerDocumentRoot]]
+==== passenger_document_root <path>
+Used in sub-URI deployment scenarios to tell Phusion Passenger where it
+should look for static files. Please refer to the following sections for
+more information:
+
+ * <<deploying_rack_to_sub_uri,Deploying Rack to a sub URI>>
+ * <<deploying_wsgi_to_sub_uri,Deploying WSGI to a sub URI>>
+ * <<deploying_rails_to_sub_uri,Deploying Rails 1 and Rails 2 to a sub URI>>
+
+This option may occur in the following places:
+
+ * In the 'http' configuration block.
+ * In a 'server' configuration block.
+ * In a 'location' configuration block.
+ * In an 'if' configuration scope.
+
+In each place, it may be specified at most once.
+
 [[PassengerSpawnMethod]]
 ==== passenger_spawn_method <string>
 [TIP]
@@ -768,8 +796,8 @@ In each place, it may be specified at most once. The default value is 'on'.
 :version: 3.0.0
 include::users_guide_snippets/enterprise_only.txt[]
 
-Enables or disables support for rolling restarts. Normally when you
-restart an application (by touching restart.txt), Phusion Passenger would
+Enables or disables support for rolling restarts through restart.txt. Normally when you
+restart an application by touching restart.txt, Phusion Passenger would
 shut down all application processes and spawn a new one. The spawning
 of a new application process could take a while, and any requests that
 come in during this time will be blocked until this first application
@@ -795,6 +823,8 @@ Rolling restarts have a few caveat however that you should be aware of:
   been restarted. It is for this reason that you should not use rolling
   restarts in development, only in production.
 
+Please note that this option is completely unrelated to the `passenger-config restart` command. That command always initiates a blocking restart, unless `--rolling-restart` is given.
+
 This option may occur in the following places:
 
  * In the 'http' configuration block.

data/doc/users_guide_snippets/environment_variables.txt

@@ -185,14 +185,14 @@ On other systems, or if you did not install Apache through the system's package
 
 NOTE: This subsection describes how to set environment variables on Nginx itself, not on apps served through Phusion Passenger for Nginx. The environment variables you set here will be passed to all apps, but you cannot customize them on a per-app basis. See also <<env_vars_passenger_apps,Setting environment variables on Phusion Passenger-served apps>>.
 
-If you installed Nginx through <<install_on_debian_ubuntu,the Brightbox packages>>, then you can define environment variables in `/etc/default/nginx`. This is a shell script so you must use the `export FOO=bar` syntax.
+If you installed Nginx through <<install_on_debian_ubuntu,the Debian or Ubuntu packages>>, then you can define environment variables in `/etc/default/nginx`. This is a shell script so you must use the `export FOO=bar` syntax.
 
 Otherwise, environment variables are best set through the script which starts Nginx. For example, if you installed Nginx from source and you used
 ifdef::apache[]
 the Nginx init script described in the link:http://www.modrails.com/documentation/Users%20guide%20Nginx.html[Phusion Passenger Users Guide, Nginx version],
 endif::apache[]
 ifdef::nginx[]
-<<nginx_init_script,the Nginx init script described earlier in this manual,
+<<nginx_init_script,the Nginx init script described earlier in this manual>>,
 endif::nginx[]
 then you should edit that script to define the environment variables. Those init scripts are regular shell scripts, so use the `export FOO=bar` syntax. Just make sure your set your environment variables before the script starts Nginx.
 

data/doc/users_guide_snippets/installation.txt

@@ -651,7 +651,7 @@ NOTE: If you run the installer with `sudo` then environment variables may not be
 On some systems, C/C++ libraries and headers that Phusion Passenger requires may be located in a non-standard directory. You can force the Phusion Passenger build system to look in those locations by injecting compiler and linker flags using the following environment variables:
 
 `EXTRA_PRE_CFLAGS`::
-	These flags are injected into all C compiler invocations that involve compiling C or C++ source files. This includes compiler invocations that compile *and* link. The flags are injected at the beginning of the command string, even before `EXTRA_PRE_LDFLAGS`.
+	These flags are injected into all C compiler invocations that involve compiling C source files. This also covers compiler invocations that compile *and* link. The flags are injected at the beginning of the command string, even before `EXTRA_PRE_LDFLAGS`.
 `EXTRA_CFLAGS`::
 	Similar to `EXTRA_PRE_CFLAGS`, but injected at the end of the command string, before `EXTRA_LDFLAGS`.
 `EXTRA_PRE_CXXFLAGS`::
@@ -659,7 +659,11 @@ On some systems, C/C++ libraries and headers that Phusion Passenger requires may
 `EXTRA_CXXFLAGS`::
 	Similar to `EXTRA_CFLAGS`, but for C++ compiler invocations.
 `EXTRA_PRE_LDFLAGS`::
-	These flags are injected into all C/C++ compiler invocations that involve linking. This includes compiler invocations that compile *and* link. The flags are injected at the beginning of the command string, but after `EXTRA_PRE_CFLAGS` and `EXTRA_PRE_CXXFLAGS`.
+	These flags are injected into all C/C++ compiler invocations that involve linking. This includes compiler invocations that compile *and* link. The flags are injected at the beginning of the command string, but after `EXTRA_PRE_CFLAGS`/`EXTRA_PRE_CXXFLAGS`.
+`EXTRA_PRE_C_LDFLAGS`::
+	These flags are injected into all C compiler invocations that involve linking, right after `EXTRA_PRE_LDFLAGS`.
+`EXTRA_PRE_CXX_LDFLAGS`::
+	Similar to `EXTRA_PRE_CXX_LDFLAGS`, but for C++ compiler invocations.
 `EXTRA_LDFLAGS`::
 	Similar to `EXTRA_PRE_LDFLAGS`, but injected at the very end of the command string, even after `EXTRA_CFLAGS` and `EXTRA_CXXFLAGS`.
 `EXTRA_C_LDFLAGS`::

data/doc/users_guide_snippets/tips.txt

@@ -477,6 +477,10 @@ Hooks may be called concurrently. For example, while the `attached_process` hook
 
 If a hook script fails -- that is, if it exits with anything other than exit code 0 -- then the error handling depends on the hook. Some hooks will abort, other hooks will ignore the error. In all cases, the result of the hook script is printed to the log.
 
+==== Compatibility
+
+Because hooks are inherently tied to the implementation of Phusion Passenger, there is no guarantee that hooks that currently work will continue to be available in the future versions of Phusion Passenger. The availability of hooks is very much tied to the specific version of Phusion Passenger.
+
 ==== Available hooks
 
 `before_watchdog_initialization`::

data/ext/apache2/Hooks.cpp

@@ -1218,7 +1218,17 @@ private:
 			size_t size;
 			
 			size = fread(buf, 1, sizeof(buf), uploadData->handle);
-			writeExact(fd, buf, size);
+			try {
+				writeExact(fd, buf, size);
+			} catch (const SystemException &e) {
+				if (e.code() == EPIPE || e.code() == ECONNRESET) {
+					// The HelperAgent stopped reading the body, probably
+					// because the application already sent EOF.
+					return;
+				} else {
+					throw e;
+				}
+			}
 		}
 	}
 
@@ -1592,6 +1602,7 @@ init_module(apr_pool_t *pconf, apr_pool_t *plog, apr_pool_t *ptemp, server_rec *
 	} catch (const thread_resource_error &e) {
 		struct rlimit lim;
 		string pthread_threads_max;
+		int ret;
 		
 		lim.rlim_cur = 0;
 		lim.rlim_max = 0;
@@ -1625,11 +1636,13 @@ init_module(apr_pool_t *pconf, apr_pool_t *plog, apr_pool_t *ptemp, server_rec *
 		
 		fprintf(stderr, "Output of 'uname -a' follows:\n");
 		fflush(stderr);
-		::system("uname -a >&2");
+		ret = ::system("uname -a >&2");
+		(void) ret; // Ignore compiler warning.
 		
 		fprintf(stderr, "\nOutput of 'ulimit -a' follows:\n");
 		fflush(stderr);
-		::system("ulimit -a >&2");
+		ret = ::system("ulimit -a >&2");
+		(void) ret; // Ignore compiler warning.
 		
 		return DECLINED;