From: Bruno Victal <mirai@makinata.eu>
To: 62490@debbugs.gnu.org
Cc: ludo@gnu.org, Bruno Victal <mirai@makinata.eu>,
maxim.cournoyer@gmail.com
Subject: [bug#62490] [PATCH v2 2/2] services: nginx: Add reopen action.
Date: Mon, 3 Apr 2023 12:58:03 +0100 [thread overview]
Message-ID: <c4d06e358b17dc5fbd5b5607890d5621b59c33d7.1680523067.git.mirai@makinata.eu> (raw)
In-Reply-To: <4027e6a1d7a59e11a7f4000b821283a1985f1dcc.1680523067.git.mirai@makinata.eu>
This is required to allow log file rotations using rottlog, etc.
* gnu/services/web.scm (nginx-shepherd-service): Add reopen shepherd action.
---
gnu/services/web.scm | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/gnu/services/web.scm b/gnu/services/web.scm
index 4fe9c2d9ab..45897d7d6f 100644
--- a/gnu/services/web.scm
+++ b/gnu/services/web.scm
@@ -840,7 +840,11 @@ (define (nginx-shepherd-service config)
the same configuration file. It is useful for situations where the same nginx
configuration file can point to different things after a reload, such as
renewed TLS certificates, or @code{include}d files.")
- (procedure (nginx-action "-s" "reload"))))))))))
+ (procedure (nginx-action "-s" "reload")))
+ (shepherd-action
+ (name 'reopen)
+ (documentation "Re-open log files.")
+ (procedure (nginx-action "-s" "reopen"))))))))))
(define nginx-service-type
(service-type (name 'nginx)
--
2.39.2
prev parent reply other threads:[~2023-04-03 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 18:51 [bug#62490] [PATCH] services: nginx: Make logging level configurable Bruno Victal
2023-03-28 14:12 ` Maxim Cournoyer
2023-03-28 14:32 ` Bruno Victal
2023-03-28 15:03 ` Maxim Cournoyer
2023-04-02 15:39 ` Ludovic Courtès
2023-04-11 17:12 ` bug#62490: " Maxim Cournoyer
2023-04-03 11:58 ` [bug#62490] [PATCH v2 1/2] " Bruno Victal
2023-04-03 11:58 ` Bruno Victal [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4d06e358b17dc5fbd5b5607890d5621b59c33d7.1680523067.git.mirai@makinata.eu \
--to=mirai@makinata.eu \
--cc=62490@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.