From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 2/7] doc: daemon: fix manpage section for nginx
Date: Fri, 24 May 2019 02:57:53 +0000 [thread overview]
Message-ID: <20190524025758.32261-3-e@80x24.org> (raw)
In-Reply-To: <20190524025758.32261-1-e@80x24.org>
The nginx manpage is in section 8.
---
Documentation/public-inbox-daemon.pod | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/public-inbox-daemon.pod b/Documentation/public-inbox-daemon.pod
index a3c97d8..47d15de 100644
--- a/Documentation/public-inbox-daemon.pod
+++ b/Documentation/public-inbox-daemon.pod
@@ -37,7 +37,7 @@ This takes an absolute path to a Unix socket or HOST:PORT
to listen on. For example, to listen to TCP connections on
port 119, use: C<-l 0.0.0.0:119>. This may also point to
a Unix socket (C<-l /path/to/http.sock>) for a reverse proxy
-like L<nginx(1)> to use.
+like L<nginx(8)> to use.
May be specified multiple times to allow listening on multiple
sockets.
@@ -77,7 +77,7 @@ Default: 1
=head1 SIGNALS
-Most of our signal handling behavior is copied from L<nginx(1)>
+Most of our signal handling behavior is copied from L<nginx(8)>
and/or L<starman(1)>; so it is possible to reuse common scripts
for managing them.
--
EW
next prev parent reply other threads:[~2019-05-24 2:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 2:57 [PATCH 0/7] various documentation fixes Eric Wong
2019-05-24 2:57 ` [PATCH 1/7] doc: index: fix miscapitalization of "SQLite" Eric Wong
2019-05-24 2:57 ` Eric Wong [this message]
2019-05-24 2:57 ` [PATCH 3/7] doc: don't barf on missing `git set-file-times' Eric Wong
2019-05-24 2:57 ` [PATCH 4/7] doc: sync .txt mtime to .pod mtime Eric Wong
2019-05-24 2:57 ` [PATCH 5/7] doc: generate manpages for some Xapian commands Eric Wong
2019-05-24 2:57 ` [PATCH 6/7] doc: xcpdb: add switch documentation Eric Wong
2019-05-24 2:57 ` [PATCH 7/7] doc: add URLs for Xapian manpages Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190524025758.32261-3-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).