From: Oleg Pykhalov <go.wigust@gmail.com>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 28776@debbugs.gnu.org
Subject: bug#28776: guix system reconfigure does not update path to nginx configuration
Date: Tue, 10 Oct 2017 13:58:46 +0300 [thread overview]
Message-ID: <874lr7fevt.fsf@gmail.com> (raw)
In-Reply-To: <87k2036zzz.fsf@lassieur.org> ("Clément Lassieur"'s message of "Tue, 10 Oct 2017 12:47:28 +0200")
Hello Clement,
Clément Lassieur <clement@lassieur.org> writes:
> Oleg Pykhalov <go.wigust@gmail.com> writes:
>
>> After changing config.scm, herd restarts NGINX with previous (on boot)
>> configuration (checked with ps). So to apply a new NGINX configuration
>> to a system, reboot is required.
>
> Quoting Ludovic from:
> https://lists.gnu.org/archive/html/guix-patches/2017-05/msg00669.html
>
> Currently ‘guix system reconfigure’ (specifically
> ‘upgrade-shepherd-services’) reloads and starts all services that are
> currently stopped, on the grounds that it would not be safe/desirable to
> simply stop any running service.
>
> So if you want NGINX to start with its new configuration, you need to
> stop it before doing the 'guix system reconfigure'.
Thank you for giving a direction! I actually tried to make 'sudo herd
restart nginx' after reconfigure, but apparently it's wrong.
I'm not sure if we need to close this bug. It wasn't obvious to
me that it related to subject “Allow services to implement a 'reload'
action”, because I tried to reload it manually :-)
next prev parent reply other threads:[~2017-10-10 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 9:37 bug#28776: guix system reconfigure does not update path to nginx configuration Oleg Pykhalov
2017-10-10 10:47 ` Clément Lassieur
2017-10-10 10:58 ` Oleg Pykhalov [this message]
2017-10-11 13:25 ` Ludovic Courtès
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=874lr7fevt.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=28776@debbugs.gnu.org \
--cc=clement@lassieur.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 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.