services: nginx: Fix ‘stop’ in cases where a custom config file is passed.

A previous commit (c7cb771cf4) fixed an issue with the nginx service to
ensure it can be stopped when started from a custom config file.
The stop command, which should have been `nginx -s stop`, was mistakenly
written as `nginx stop`, which means that `herd stop nginx` still fails
in the given case. This commit corrects that typo.

* gnu/services/web.scm (nginx-shepherd-service): In ‘stop’, correctly
  call “nginx -s stop” when ‘value’ is not a process.

Fixes: guix/guix#7061
Reported-by: Dan Littlewood
Change-Id: I3055fc24084d30da969afd508861d2423a396ced
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Merges: #8128

1 files changed, 1 insertions, 1 deletions

diff --git a/gnu/services/web.scm b/gnu/services/web.scm
index 948d8064c6a..4d2f78bee19 100644
--- a/gnu/services/web.scm
+++ b/gnu/services/web.scm
@@ -995,7 +995,7 @@ of index files."
                       ;; "nginx -s stop".
                       (if (process? value)
                           (terminate-process (process-id value) SIGTERM)
-                          (#$(nginx-action "stop")))))
+                          (#$(nginx-action "-s" "stop")))))
 
             (actions
               (list