From: Ricardo Wurmus <rekado@elephly.net>
To: myglc2@gmail.com
Cc: help-guix <help-guix@gnu.org>
Subject: Re: reconfiguring
Date: Wed, 14 Feb 2018 08:49:34 +0100 [thread overview]
Message-ID: <87d11880z5.fsf@elephly.net> (raw)
In-Reply-To: <861shocvod.fsf@gmail.com>
myglc2@gmail.com writes:
> On 02/13/2018 at 21:32 Andreas Enge writes:
>
>> On Tue, Feb 13, 2018 at 02:03:58PM -0500, Leo Famulari wrote:
>>> But, it doesn't try to stop and restart those services in case of any
>>> relevant changes, right? Doesn't that require a reboot?
>>
>> Yes, I understood so. I had the problem with my nginx server recently.
>> In that case, I needed to stop it before upgrading, and then it was
>> restarted automatically. However, when it was not stopped, it continued
>> running with the old configuration. It is not quite clear to me whether
>> this is a bug or a feature. I tend more towards bug... It is definitely
>> in contrast to what happens in Debian, for instance.
>
> This bug/feature bit me (also Debian user) recently ;-)
>
> Is this by design? Or a limitation if the current implementation?
It’s a bug; bug 22039 to be exact.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-02-14 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 15:35 reconfiguring Catonano
2018-02-13 18:25 ` reconfiguring Ricardo Wurmus
2018-02-13 19:03 ` reconfiguring Leo Famulari
2018-02-13 19:11 ` reconfiguring Ricardo Wurmus
2018-02-13 19:18 ` reconfiguring Carlo Zancanaro
2018-02-13 19:22 ` reconfiguring Leo Famulari
2018-02-13 20:32 ` reconfiguring Andreas Enge
2018-02-13 23:32 ` reconfiguring myglc2
2018-02-14 7:49 ` Ricardo Wurmus [this message]
2018-02-13 19:10 ` reconfiguring Carlo Zancanaro
2018-02-13 20:33 ` reconfiguring Ricardo Wurmus
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d11880z5.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=myglc2@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.
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).