user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 3/3] examples/unsubscribe-psgi@.service: disable worker processes
Date: Sat, 21 May 2016 04:24:35 +0000	[thread overview]
Message-ID: <20160521042435.12800-2-e@80x24.org> (raw)
In-Reply-To: <20160520213655.19381-1-e@80x24.org>

This unsubscribe PSGI endpoint should never incur enough load to
justify using multiple worker processes.  If it's unstable and
crashes, systemd can automatically restart it.
---
 examples/unsubscribe-psgi@.service | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/examples/unsubscribe-psgi@.service b/examples/unsubscribe-psgi@.service
index f588886..2dc4270 100644
--- a/examples/unsubscribe-psgi@.service
+++ b/examples/unsubscribe-psgi@.service
@@ -11,7 +11,7 @@ After = unsubscribe-psgi.socket
 [Service]
 # any PSGI server ought to work,
 # but public-inbox-httpd supports socket activation like unsubscribe.milter
-ExecStart = /usr/local/bin/public-inbox-httpd /etc/unsubscribe.psgi
+ExecStart = /usr/local/bin/public-inbox-httpd -W0 /etc/unsubscribe.psgi
 Sockets = unsubscribe-psgi.socket
 # we need to modify the mlmmj spool
 User = mlmmj

  parent reply	other threads:[~2016-05-21  4:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 21:36 [PATCH] unsubscribe: get off mah lawn^H^H^Hist Eric Wong
2016-05-21  4:24 ` [PATCH 2/3] unsubscribe: bad URL fixup Eric Wong
2016-05-21  4:24 ` Eric Wong [this message]
2016-05-27  8:08 ` [PATCH] unsubscribe.milter: use default postfork dispatcher Eric Wong
2016-06-07 13:18 ` Merge branch 'unsubscribe' Eric Wong
2016-06-07 13:20   ` [PATCH] unsubscribe.psgi: disable confirmation Eric Wong
2016-06-07 13:21   ` [PATCH] unsubscribe.milter: implement archive blacklist Eric Wong
2016-06-07 13:40   ` [PATCH] unsubscribe: fix off-by-one error 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: https://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=20160521042435.12800-2-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).