unicorn 5.4.0 → 5.7.0

data/man/man1/unicorn.1

@@ -1,4 +1,5 @@
 .TH "UNICORN" "1" "September 15, 2009" "Unicorn User Manual" ""
+.hy
 .SH NAME
 .PP
 unicorn \- a rackup\-like command to launch the Unicorn HTTP server
@@ -8,74 +9,73 @@ unicorn [\-c CONFIG_FILE] [\-E RACK_ENV] [\-D] [RACKUP_FILE]
 .SH DESCRIPTION
 .PP
 A rackup(1)\-like command to launch Rack applications using Unicorn.
-It is expected to be started in your application root (APP_ROOT), but
-the "working_directory" directive may be used in the CONFIG_FILE.
+It is expected to be started in your application root (APP_ROOT),
+but the "working_directory" directive may be used in the CONFIG_FILE.
 .PP
-While unicorn takes a myriad of command\-line options for compatibility
-with ruby(1) and rackup(1), it is recommended to stick to the few
-command\-line options specified in the SYNOPSIS and use the CONFIG_FILE
-as much as possible.
+While unicorn takes a myriad of command\-line options for
+compatibility with ruby(1) and rackup(1), it is recommended to stick
+to the few command\-line options specified in the SYNOPSIS and use
+the CONFIG_FILE as much as possible.
 .SH RACKUP FILE
 .PP
-This defaults to "config.ru" in APP_ROOT.
-It should be the same file used by rackup(1) and other Rack launchers,
-it uses the \f[I]Rack::Builder\f[] DSL.
+This defaults to "config.ru" in APP_ROOT.  It should be the same
+file used by rackup(1) and other Rack launchers, it uses the
+\f[I]Rack::Builder\f[] DSL.
 .PP
-Embedded command\-line options are mostly parsed for compatibility with
-rackup(1) but strongly discouraged.
+Embedded command\-line options are mostly parsed for compatibility
+with rackup(1) but strongly discouraged.
 .SH UNICORN OPTIONS
 .TP
 .B \-c, \-\-config\-file CONFIG_FILE
-Path to the Unicorn\-specific config file.
-The config file is implemented as a Ruby DSL, so Ruby code may executed.
-See the RDoc/ri for the \f[I]Unicorn::Configurator\f[] class for the
-full list of directives available from the DSL.
-Using an absolute path for for CONFIG_FILE is recommended as it makes
-multiple instances of Unicorn easily distinguishable when viewing ps(1)
-output.
+Path to the Unicorn\-specific config file.  The config file is
+implemented as a Ruby DSL, so Ruby code may executed.
+See the RDoc/ri for the \f[I]Unicorn::Configurator\f[] class for the full
+list of directives available from the DSL.
+Using an absolute path for for CONFIG_FILE is recommended as it
+makes multiple instances of Unicorn easily distinguishable when
+viewing ps(1) output.
 .RS
 .RE
 .TP
 .B \-D, \-\-daemonize
-Run daemonized in the background.
-The process is detached from the controlling terminal and stdin is
-redirected to "/dev/null".
-Unlike many common UNIX daemons, we do not chdir to "/" upon
-daemonization to allow more control over the startup/upgrade process.
-Unless specified in the CONFIG_FILE, stderr and stdout will also be
-redirected to "/dev/null".
+Run daemonized in the background.  The process is detached from
+the controlling terminal and stdin is redirected to "/dev/null".
+Unlike many common UNIX daemons, we do not chdir to "/"
+upon daemonization to allow more control over the startup/upgrade
+process.
+Unless specified in the CONFIG_FILE, stderr and stdout will
+also be redirected to "/dev/null".
 .RS
 .RE
 .TP
 .B \-E, \-\-env RACK_ENV
-Run under the given RACK_ENV.
-See the RACK ENVIRONMENT section for more details.
+Run under the given RACK_ENV.  See the RACK ENVIRONMENT section
+for more details.
 .RS
 .RE
 .TP
 .B \-l, \-\-listen ADDRESS
-Listens on a given ADDRESS.
-ADDRESS may be in the form of HOST:PORT or PATH, HOST:PORT is taken to
-mean a TCP socket and PATH is meant to be a path to a UNIX domain
-socket.
-Defaults to "0.0.0.0:8080" (all addresses on TCP port 8080) For
-production deployments, specifying the "listen" directive in CONFIG_FILE
-is recommended as it allows fine\-tuning of socket options.
+Listens on a given ADDRESS.  ADDRESS may be in the form of
+HOST:PORT or PATH, HOST:PORT is taken to mean a TCP socket
+and PATH is meant to be a path to a UNIX domain socket.
+Defaults to "0.0.0.0:8080" (all addresses on TCP port 8080)
+For production deployments, specifying the "listen" directive in
+CONFIG_FILE is recommended as it allows fine\-tuning of socket
+options.
 .RS
 .RE
 .TP
 .B \-N, \-\-no\-default\-middleware
-Disables loading middleware implied by RACK_ENV.
-This bypasses the configuration documented in the RACK ENVIRONMENT
-section, but still allows RACK_ENV to be used for
-application/framework\-specific purposes.
+Disables loading middleware implied by RACK_ENV.  This bypasses the
+configuration documented in the RACK ENVIRONMENT section, but still
+allows RACK_ENV to be used for application/framework\-specific purposes.
 .RS
 .RE
 .SH RACKUP COMPATIBILITY OPTIONS
 .TP
 .B \-o, \-\-host HOST
-Listen on a TCP socket belonging to HOST, default is "0.0.0.0" (all
-addresses).
+Listen on a TCP socket belonging to HOST, default is
+"0.0.0.0" (all addresses).
 If specified multiple times on the command\-line, only the
 last\-specified value takes effect.
 This option only exists for compatibility with the rackup(1) command,
@@ -85,8 +85,8 @@ use of "\-l"/"\-\-listen" switch is recommended instead.
 .TP
 .B \-p, \-\-port PORT
 Listen on the specified TCP PORT, default is 8080.
-If specified multiple times on the command\-line, only the
-last\-specified value takes effect.
+If specified multiple times on the command\-line, only the last\-specified
+value takes effect.
 This option only exists for compatibility with the rackup(1) command,
 use of "\-l"/"\-\-listen" switch is recommended instead.
 .RS
@@ -99,9 +99,8 @@ No\-op, this exists only for compatibility with rackup(1).
 .SH RUBY OPTIONS
 .TP
 .B \-e, \-\-eval LINE
-Evaluate a LINE of Ruby code.
-This evaluation happens immediately as the command\-line is being
-parsed.
+Evaluate a LINE of Ruby code.  This evaluation happens
+immediately as the command\-line is being parsed.
 .RS
 .RE
 .TP
@@ -116,18 +115,17 @@ Turn on verbose warnings, the $VERBOSE variable is set to true.
 .RE
 .TP
 .B \-I, \-\-include PATH
-specify
-\f[I]L\f[]\f[I]O\f[]\f[I]A\f[]\f[I]D\f[]~\f[I]P\f[]~\f[I]A\f[]\f[I]T\f[]\f[I]H\f[].\f[I]P\f[]\f[I]A\f[]\f[I]T\f[]\f[I]H\f[]\f[I]w\f[]\f[I]i\f[]\f[I]l\f[]\f[I]l\f[]\f[I]b\f[]\f[I]e\f[]\f[I]p\f[]\f[I]r\f[]\f[I]e\f[]\f[I]p\f[]\f[I]e\f[]\f[I]n\f[]\f[I]d\f[]\f[I]e\f[]\f[I]d\f[]\f[I]t\f[]\f[I]o\f[]LOAD_PATH.
+specify $LOAD_PATH.  PATH will be prepended to $LOAD_PATH.
 The \[aq]:\[aq] character may be used to delimit multiple directories.
-This directive may be used more than once.
-Modifications to $LOAD_PATH take place immediately and in the order they
-were specified on the command\-line.
+This directive may be used more than once.  Modifications to
+$LOAD_PATH take place immediately and in the order they were
+specified on the command\-line.
 .RS
 .RE
 .TP
 .B \-r, \-\-require LIBRARY
-require a specified LIBRARY before executing the application.
-The "require" statement will be executed immediately and in the order
+require a specified LIBRARY before executing the application.  The
+"require" statement will be executed immediately and in the order
 they were specified on the command\-line.
 .RS
 .RE
@@ -139,15 +137,15 @@ HUP \- reload config file, app, and gracefully restart all workers
 .IP \[bu] 2
 INT/TERM \- quick shutdown, kills all workers immediately
 .IP \[bu] 2
-QUIT \- graceful shutdown, waits for workers to finish their current
-request before finishing.
+QUIT \- graceful shutdown, waits for workers to finish their
+current request before finishing.
 .IP \[bu] 2
-USR1 \- reopen all logs owned by the master and all workers See
-Unicorn::Util.reopen_logs for what is considered a log.
+USR1 \- reopen all logs owned by the master and all workers
+See Unicorn::Util.reopen_logs for what is considered a log.
 .IP \[bu] 2
-USR2 \- reexecute the running binary.
-A separate QUIT should be sent to the original process once the child is
-verified to be up and running.
+USR2 \- reexecute the running binary.  A separate QUIT
+should be sent to the original process once the child is verified to
+be up and running.
 .IP \[bu] 2
 WINCH \- gracefully stops workers but keep the master running.
 This will only work for daemonized processes.
@@ -156,7 +154,7 @@ TTIN \- increment the number of worker processes by one
 .IP \[bu] 2
 TTOU \- decrement the number of worker processes by one
 .PP
-See the SIGNALS (https://bogomips.org/unicorn/SIGNALS.html) document for
+See the SIGNALS (https://yhbt.net/unicorn/SIGNALS.html) document for
 full description of all signals used by Unicorn.
 .SH RACK ENVIRONMENT
 .PP
@@ -164,56 +162,61 @@ Accepted values of RACK_ENV and the middleware they automatically load
 (outside of RACKUP_FILE) are exactly as those in rackup(1):
 .IP \[bu] 2
 development \- loads Rack::CommonLogger, Rack::ShowExceptions, and
-Rack::Lint middleware
+              Rack::Lint middleware
 .IP \[bu] 2
 deployment \- loads Rack::CommonLogger middleware
 .IP \[bu] 2
 none \- loads no middleware at all, relying entirely on RACKUP_FILE
 .PP
-All unrecognized values for RACK_ENV are assumed to be "none".
-Production deployments are strongly encouraged to use "deployment" or
-"none" for maximum performance.
+All unrecognized values for RACK_ENV are assumed to be
+"none".  Production deployments are strongly encouraged to use
+"deployment" or "none" for maximum performance.
 .PP
-As of Unicorn 0.94.0, RACK_ENV is exported as a process\-wide
-environment variable as well.
-While not current a part of the Rack specification as of Rack 1.0.1,
-this has become a de facto standard in the Rack world.
+As of Unicorn 0.94.0, RACK_ENV is exported as a process\-wide environment
+variable as well.  While not current a part of the Rack specification as
+of Rack 1.0.1, this has become a de facto standard in the Rack world.
 .PP
 Note the Rack::ContentLength and Rack::Chunked middlewares are also
 loaded by "deployment" and "development", but no other values of
-RACK_ENV.
-If needed, they must be individually specified in the RACKUP_FILE, some
-frameworks do not require them.
+RACK_ENV.  If needed, they must be individually specified in the
+RACKUP_FILE, some frameworks do not require them.
 .SH ENVIRONMENT VARIABLES
 .PP
 The RACK_ENV variable is set by the aforementioned \-E switch.
-All application or library\-specific environment variables (e.g.
-TMPDIR) may always be set in the Unicorn CONFIG_FILE in addition to the
-spawning shell.
-When transparently upgrading Unicorn, all environment variables set in
-the old master process are inherited by the new master process.
+All application or library\-specific environment variables (e.g. TMPDIR)
+may always be set in the Unicorn CONFIG_FILE in addition to the spawning
+shell.  When transparently upgrading Unicorn, all environment variables
+set in the old master process are inherited by the new master process.
 Unicorn only uses (and will overwrite) the UNICORN_FD environment
 variable internally when doing transparent upgrades.
 .PP
 UNICORN_FD is a comma\-delimited list of one or more file descriptors
-used to implement USR2 upgrades.
-Init systems may bind listen sockets itself and spawn unicorn with
-UNICORN_FD set to the file descriptor numbers of the listen socket(s).
+used to implement USR2 upgrades.  Init systems may bind listen sockets
+itself and spawn unicorn with UNICORN_FD set to the file descriptor
+numbers of the listen socket(s).
 .PP
 As of unicorn 5.0, LISTEN_PID and LISTEN_FDS are used for socket
-activation as documented in the sd_listen_fds(3) manpage.
-Users relying on this feature do not need to specify a listen socket in
+activation as documented in the sd_listen_fds(3) manpage.  Users
+relying on this feature do not need to specify a listen socket in
 the unicorn config file.
 .SH SEE ALSO
 .IP \[bu] 2
 \f[I]Rack::Builder\f[] ri/RDoc
 .IP \[bu] 2
 \f[I]Unicorn::Configurator\f[] ri/RDoc
+.UR https://yhbt.net/unicorn/Unicorn/Configurator.html
+.UE
 .IP \[bu] 2
-Unicorn RDoc (https://bogomips.org/unicorn/)
+unicorn RDoc
+.UR https://yhbt.net/unicorn/
+.UE
 .IP \[bu] 2
-Rack RDoc (http://www.rubydoc.info/github/rack/rack/)
+Rack RDoc
+.UR https://www.rubydoc.info/github/rack/rack/
+.UE
 .IP \[bu] 2
-Rackup HowTo (https://github.com/rack/rack/wiki/tutorial-rackup-howto)
+Rackup HowTo
+.UR https://github.com/rack/rack/wiki/(tutorial)-rackup-howto
+.UE
 .SH AUTHORS
-The Unicorn Community <unicorn-public@bogomips.org>.
+The Unicorn Community <unicorn-public@yhbt.net>.

data/man/man1/unicorn_rails.1

@@ -1,4 +1,5 @@
 .TH "UNICORN_RAILS" "1" "September 17, 2009" "Unicorn User Manual" ""
+.hy
 .SH NAME
 .PP
 unicorn_rails \- unicorn launcher for Rails 1.x and 2.x users
@@ -7,17 +8,12 @@ unicorn_rails \- unicorn launcher for Rails 1.x and 2.x users
 unicorn_rails [\-c CONFIG_FILE] [\-E RAILS_ENV] [\-D] [RACKUP_FILE]
 .SH DESCRIPTION
 .PP
-A rackup(1)\-like command to launch Rails applications using Unicorn.
-It is expected to be started in your Rails application root
-(RAILS_ROOT), but the "working_directory" directive may be used in the
-CONFIG_FILE.
+A rackup(1)\-like command to launch ancient Rails (2.x and earlier)
+applications using Unicorn.  Rails 3 (and later) support Rack natively,
+so users are encouraged to use unicorn(1) instead of unicorn_rails(1).
 .PP
-It is designed to help Rails 1.x and 2.y users transition to Rack, but
-it is NOT needed for Rails 3 applications.
-Rails 3 users are encouraged to use unicorn(1) instead of
-unicorn_rails(1).
-Users of Rails 1.x/2.y may also use unicorn(1) instead of
-unicorn_rails(1).
+It is expected to be started in your Rails application root (RAILS_ROOT),
+but the "working_directory" directive may be used in the CONFIG_FILE.
 .PP
 The outward interface resembles rackup(1), the internals and default
 middleware loading is designed like the \f[C]script/server\f[] command
@@ -30,56 +26,55 @@ as much as possible.
 .SH UNICORN OPTIONS
 .TP
 .B \-c, \-\-config\-file CONFIG_FILE
-Path to the Unicorn\-specific config file.
-The config file is implemented as a Ruby DSL, so Ruby code may executed.
-See the RDoc/ri for the \f[I]Unicorn::Configurator\f[] class for the
-full list of directives available from the DSL.
-Using an absolute path for for CONFIG_FILE is recommended as it makes
-multiple instances of Unicorn easily distinguishable when viewing ps(1)
-output.
+Path to the Unicorn\-specific config file.  The config file is
+implemented as a Ruby DSL, so Ruby code may executed.
+See the RDoc/ri for the \f[I]Unicorn::Configurator\f[] class for the full
+list of directives available from the DSL.
+Using an absolute path for for CONFIG_FILE is recommended as it
+makes multiple instances of Unicorn easily distinguishable when
+viewing ps(1) output.
 .RS
 .RE
 .TP
 .B \-D, \-\-daemonize
-Run daemonized in the background.
-The process is detached from the controlling terminal and stdin is
-redirected to "/dev/null".
+Run daemonized in the background.  The process is detached from
+the controlling terminal and stdin is redirected to "/dev/null".
 Unlike many common UNIX daemons, we do not chdir to "/" upon
-daemonization to allow more control over the startup/upgrade process.
-Unless specified in the CONFIG_FILE, stderr and stdout will also be
-redirected to "/dev/null".
+daemonization to allow more control over the startup/upgrade
+process.
+Unless specified in the CONFIG_FILE, stderr and stdout will
+also be redirected to "/dev/null".
 Daemonization will \f[I]skip\f[] loading of the
-\f[I]Rails::Rack::LogTailer\f[] middleware under Rails >= 2.3.x.
+\f[I]Rails::Rack::LogTailer\f[]
+middleware under Rails >= 2.3.x.
 By default, unicorn_rails(1) will create a PID file in
-\f[I]"RAILS_ROOT/tmp/pids/unicorn.pid"\f[].
-You may override this by specifying the "pid" directive to override this
-Unicorn config file.
+\f[I]"RAILS_ROOT/tmp/pids/unicorn.pid"\f[].  You may override this
+by specifying the "pid" directive to override this Unicorn config file.
 .RS
 .RE
 .TP
 .B \-E, \-\-env RAILS_ENV
-Run under the given RAILS_ENV.
-This sets the RAILS_ENV environment variable.
-Acceptable values are exactly those you expect in your Rails
+Run under the given RAILS_ENV.  This sets the RAILS_ENV environment
+variable.  Acceptable values are exactly those you expect in your Rails
 application, typically "development" or "production".
 .RS
 .RE
 .TP
 .B \-l, \-\-listen ADDRESS
-Listens on a given ADDRESS.
-ADDRESS may be in the form of HOST:PORT or PATH, HOST:PORT is taken to
-mean a TCP socket and PATH is meant to be a path to a UNIX domain
-socket.
+Listens on a given ADDRESS.  ADDRESS may be in the form of
+HOST:PORT or PATH, HOST:PORT is taken to mean a TCP socket
+and PATH is meant to be a path to a UNIX domain socket.
 Defaults to "0.0.0.0:8080" (all addresses on TCP port 8080).
 For production deployments, specifying the "listen" directive in
-CONFIG_FILE is recommended as it allows fine\-tuning of socket options.
+CONFIG_FILE is recommended as it allows fine\-tuning of socket
+options.
 .RS
 .RE
 .SH RACKUP COMPATIBILITY OPTIONS
 .TP
 .B \-o, \-\-host HOST
-Listen on a TCP socket belonging to HOST, default is "0.0.0.0" (all
-addresses).
+Listen on a TCP socket belonging to HOST, default is
+"0.0.0.0" (all addresses).
 If specified multiple times on the command\-line, only the
 last\-specified value takes effect.
 This option only exists for compatibility with the rackup(1) command,
@@ -89,8 +84,8 @@ use of "\-l"/"\-\-listen" switch is recommended instead.
 .TP
 .B \-p, \-\-port PORT
 Listen on the specified TCP PORT, default is 8080.
-If specified multiple times on the command\-line, only the
-last\-specified value takes effect.
+If specified multiple times on the command\-line, only the last\-specified
+value takes effect.
 This option only exists for compatibility with the rackup(1) command,
 use of "\-l"/"\-\-listen" switch is recommended instead.
 .RS
@@ -98,17 +93,16 @@ use of "\-l"/"\-\-listen" switch is recommended instead.
 .TP
 .B \-\-path PATH
 Mounts the Rails application at the given PATH (instead of "/").
-This is equivalent to setting the RAILS_RELATIVE_URL_ROOT environment
-variable.
-This is only supported under Rails 2.3 or later at the moment.
+This is equivalent to setting the RAILS_RELATIVE_URL_ROOT
+environment variable.  This is only supported under Rails 2.3
+or later at the moment.
 .RS
 .RE
 .SH RUBY OPTIONS
 .TP
 .B \-e, \-\-eval LINE
-Evaluate a LINE of Ruby code.
-This evaluation happens immediately as the command\-line is being
-parsed.
+Evaluate a LINE of Ruby code.  This evaluation happens
+immediately as the command\-line is being parsed.
 .RS
 .RE
 .TP
@@ -125,46 +119,42 @@ Turn on verbose warnings, the $VERBOSE variable is set to true.
 .RE
 .TP
 .B \-I, \-\-include PATH
-specify
-\f[I]L\f[]\f[I]O\f[]\f[I]A\f[]\f[I]D\f[]~\f[I]P\f[]~\f[I]A\f[]\f[I]T\f[]\f[I]H\f[].\f[I]P\f[]\f[I]A\f[]\f[I]T\f[]\f[I]H\f[]\f[I]w\f[]\f[I]i\f[]\f[I]l\f[]\f[I]l\f[]\f[I]b\f[]\f[I]e\f[]\f[I]p\f[]\f[I]r\f[]\f[I]e\f[]\f[I]p\f[]\f[I]e\f[]\f[I]n\f[]\f[I]d\f[]\f[I]e\f[]\f[I]d\f[]\f[I]t\f[]\f[I]o\f[]LOAD_PATH.
+specify $LOAD_PATH.  PATH will be prepended to $LOAD_PATH.
 The \[aq]:\[aq] character may be used to delimit multiple directories.
-This directive may be used more than once.
-Modifications to $LOAD_PATH take place immediately and in the order they
-were specified on the command\-line.
+This directive may be used more than once.  Modifications to
+$LOAD_PATH take place immediately and in the order they were
+specified on the command\-line.
 .RS
 .RE
 .TP
 .B \-r, \-\-require LIBRARY
-require a specified LIBRARY before executing the application.
-The "require" statement will be executed immediately and in the order
+require a specified LIBRARY before executing the application.  The
+"require" statement will be executed immediately and in the order
 they were specified on the command\-line.
 .RS
 .RE
 .SH RACKUP FILE
 .PP
-This defaults to "config.ru" in RAILS_ROOT.
-It should be the same file used by rackup(1) and other Rack launchers,
-it uses the \f[I]Rack::Builder\f[] DSL.
-Unlike many other Rack applications, RACKUP_FILE is completely
-\f[I]optional\f[] for Rails, but may be used to disable some of the
-default middleware for performance.
+This defaults to "config.ru" in RAILS_ROOT.  It should be the same
+file used by rackup(1) and other Rack launchers, it uses the
+\f[I]Rack::Builder\f[] DSL.  Unlike many other Rack applications, RACKUP_FILE
+is completely \f[I]optional\f[] for Rails, but may be used to disable
+some of the default middleware for performance.
 .PP
-Embedded command\-line options are mostly parsed for compatibility with
-rackup(1) but strongly discouraged.
+Embedded command\-line options are mostly parsed for compatibility
+with rackup(1) but strongly discouraged.
 .SH ENVIRONMENT VARIABLES
 .PP
-The RAILS_ENV variable is set by the aforementioned \-E switch.
-The RAILS_RELATIVE_URL_ROOT is set by the aforementioned \-\-path
-switch.
+The RAILS_ENV variable is set by the aforementioned \-E switch.  The
+RAILS_RELATIVE_URL_ROOT is set by the aforementioned \-\-path switch.
 Either of these variables may also be set in the shell or the Unicorn
-CONFIG_FILE.
-All application or library\-specific environment variables (e.g.
-TMPDIR, RAILS_ASSET_ID) may always be set in the Unicorn CONFIG_FILE in
-addition to the spawning shell.
-When transparently upgrading Unicorn, all environment variables set in
-the old master process are inherited by the new master process.
-Unicorn only uses (and will overwrite) the UNICORN_FD environment
-variable internally when doing transparent upgrades.
+CONFIG_FILE.  All application or library\-specific environment variables
+(e.g. TMPDIR, RAILS_ASSET_ID) may always be set in the Unicorn
+CONFIG_FILE in addition to the spawning shell.  When transparently
+upgrading Unicorn, all environment variables set in the old master
+process are inherited by the new master process.  Unicorn only uses (and
+will overwrite) the UNICORN_FD environment variable internally when
+doing transparent upgrades.
 .SH SIGNALS
 .PP
 The following UNIX signals may be sent to the master process:
@@ -176,12 +166,12 @@ INT/TERM \- quick shutdown, kills all workers immediately
 QUIT \- graceful shutdown, waits for workers to finish their current
 request before finishing.
 .IP \[bu] 2
-USR1 \- reopen all logs owned by the master and all workers See
-Unicorn::Util.reopen_logs for what is considered a log.
+USR1 \- reopen all logs owned by the master and all workers
+See Unicorn::Util.reopen_logs for what is considered a log.
 .IP \[bu] 2
-USR2 \- reexecute the running binary.
-A separate QUIT should be sent to the original process once the child is
-verified to be up and running.
+USR2 \- reexecute the running binary.  A separate QUIT
+should be sent to the original process once the child is verified to
+be up and running.
 .IP \[bu] 2
 WINCH \- gracefully stops workers but keep the master running.
 This will only work for daemonized processes.
@@ -190,7 +180,7 @@ TTIN \- increment the number of worker processes by one
 .IP \[bu] 2
 TTOU \- decrement the number of worker processes by one
 .PP
-See the SIGNALS (https://bogomips.org/unicorn/SIGNALS.html) document for
+See the SIGNALS (https://yhbt.net/unicorn/SIGNALS.html) document for
 full description of all signals used by Unicorn.
 .SH SEE ALSO
 .IP \[bu] 2
@@ -199,11 +189,19 @@ unicorn(1)
 \f[I]Rack::Builder\f[] ri/RDoc
 .IP \[bu] 2
 \f[I]Unicorn::Configurator\f[] ri/RDoc
+.UR https://yhbt.net/unicorn/Unicorn/Configurator.html
+.UE
 .IP \[bu] 2
-Unicorn RDoc (https://bogomips.org/unicorn/)
+unicorn RDoc
+.UR https://yhbt.net/unicorn/
+.UE
 .IP \[bu] 2
-Rack RDoc (http://www.rubydoc.info/github/rack/rack/)
+Rack RDoc
+.UR https://www.rubydoc.info/github/rack/rack/
+.UE
 .IP \[bu] 2
-Rackup HowTo (https://github.com/rack/rack/wiki/tutorial-rackup-howto)
+Rackup HowTo
+.UR https://github.com/rack/rack/wiki/(tutorial)-rackup-howto
+.UE
 .SH AUTHORS
-The Unicorn Community <unicorn-public@bogomips.org>.
+The Unicorn Community <unicorn-public@yhbt.net>.

data/t/GNUmakefile

@@ -1,74 +1,5 @@
-# we can run tests in parallel with GNU make
+# there used to be more, here, but we stopped relying on recursive make
 all::
+	$(MAKE) -C .. test-integration
 
-pid := $(shell echo $$PPID)
-
-RUBY = ruby
-RAKE = rake
--include ../local.mk
-ifeq ($(RUBY_VERSION),)
-  RUBY_VERSION := $(shell $(RUBY) -e 'puts RUBY_VERSION')
-endif
-
-ifeq ($(RUBY_VERSION),)
-  $(error unable to detect RUBY_VERSION)
-endif
-
-RUBY_ENGINE := $(shell $(RUBY) -e 'puts((RUBY_ENGINE rescue "ruby"))')
-export RUBY_ENGINE
-
-MYLIBS := $(RUBYLIB)
-
-T = $(wildcard t[0-9][0-9][0-9][0-9]-*.sh)
-
-all:: $(T)
-
-# can't rely on "set -o pipefail" since we don't require bash or ksh93 :<
-t_pfx = trash/$@-$(RUBY_ENGINE)-$(RUBY_VERSION)
-TEST_OPTS =
-# TRACER = strace -f -o $(t_pfx).strace -s 100000
-# TRACER = /usr/bin/time -o $(t_pfx).time
-
-ifdef V
-  ifeq ($(V),2)
-    TEST_OPTS += --trace
-  else
-    TEST_OPTS += --verbose
-  endif
-endif
-
-random_blob:
-	dd if=/dev/urandom bs=1M count=30 of=$@.$(pid)
-	mv $@.$(pid) $@
-
-$(T): random_blob
-
-dependencies := socat curl
-deps := $(addprefix .dep+,$(dependencies))
-$(deps): dep_bin = $(lastword $(subst +, ,$@))
-$(deps):
-	@which $(dep_bin) > $@.$(pid) 2>/dev/null || :
-	@test -s $@.$(pid) || \
-	  { echo >&2 "E '$(dep_bin)' not found in PATH=$(PATH)"; exit 1; }
-	@mv $@.$(pid) $@
-dep: $(deps)
-
-test_prefix := $(CURDIR)/../test/$(RUBY_ENGINE)-$(RUBY_VERSION)
-$(test_prefix)/.stamp:
-	$(MAKE) -C .. test-install
-
-$(T): export RUBY := $(RUBY)
-$(T): export RAKE := $(RAKE)
-$(T): export PATH := $(test_prefix)/bin:$(PATH)
-$(T): export RUBYLIB := $(test_prefix)/lib:$(MYLIBS)
-$(T): dep $(test_prefix)/.stamp trash/.gitignore
-	$(TRACER) $(SHELL) $(SH_TEST_OPTS) $@ $(TEST_OPTS)
-
-trash/.gitignore:
-	mkdir -p $(@D)
-	echo '*' > $@
-
-clean:
-	$(RM) -r trash/*
-
-.PHONY: $(T) clean
+.PHONY: all

data/t/README

@@ -10,17 +10,17 @@ comfortable writing integration tests with.
 
 == Requirements
 
-* {Ruby 1.9.3+}[https://www.ruby-lang.org/] (duh!)
-* {GNU make}[http://www.gnu.org/software/make/]
+* {Ruby 1.9.3+}[https://www.ruby-lang.org/en/] (duh!)
+* {GNU make}[https://www.gnu.org/software/make/]
 * {socat}[http://www.dest-unreach.org/socat/]
-* {curl}[http://curl.haxx.se/]
+* {curl}[https://curl.haxx.se/]
 * standard UNIX shell utilities (Bourne sh, awk, sed, grep, ...)
 
 We do not use bashisms or any non-portable, non-POSIX constructs
 in our shell code.  We use the "pipefail" option if available and
 mainly test with {ksh}[http://kornshell.com/], but occasionally
 with {dash}[http://gondor.apana.org.au/~herbert/dash/] and
-{bash}[http://www.gnu.org/software/bash/], too.
+{bash}[https://www.gnu.org/software/bash/], too.
 
 == Running Tests