From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Ryan Moe <ryan.moe@gmail.com>, 27889@debbugs.gnu.org
Subject: bug#27889: Polkit actions are not updated after guix system reconfigure
Date: Tue, 01 Aug 2017 12:03:34 +0200 [thread overview]
Message-ID: <87vam7r4eh.fsf@gnu.org> (raw)
In-Reply-To: <20170731233404.691437c0@scratchpost.org> (Danny Milosavljevic's message of "Mon, 31 Jul 2017 23:34:04 +0200")
Hello,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> But gnu/services/shepherd.scm shepherd-service-file could be extended to provide a "restart" action (shepherd itself already supports it).
>
> The general format for shepherd is:
>
> (register-services
> (make <service>
> #:provides '(apache-2.0 apache httpd)
> #:requires '()
> #:start (...)
> #:stop (...)
> #:actions (make-actions
> (restart (...)))))
> ^^^^^^^^^^^^^
>
> But the Guix <shepherd-service> record, which is the source that is eventually compiled to the above, neither has an "actions" slot nor a "restart" slot. It would have to be extended with one.
>
> I wonder whether it would make sense to make shepherd automatically default to a SIGHUP restart action for daemonized processes instead, though. It's not exactly rare for daemons to provide that.
>
> Also, does "guix system reconfigure" already call this restart action if it's present?
Not yet, but it should. I think the patches at
<https://bugs.gnu.org/26830> would be sufficient if the action boils
down to sending SIGHUP. Perhaps time to revive that patch set!
Ludo’.
prev parent reply other threads:[~2017-08-01 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 21:08 bug#27889: Polkit actions are not updated after guix system reconfigure Ryan Moe
2017-07-31 21:34 ` Danny Milosavljevic
2017-07-31 23:10 ` Ryan Moe
2017-08-01 7:17 ` Danny Milosavljevic
2017-08-01 10:03 ` Ludovic Courtès [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
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=87vam7r4eh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27889@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=ryan.moe@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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).