From: Vincent Legoll <vincent.legoll@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Proxy settings wrt guix daemon
Date: Sat, 4 Apr 2020 00:29:10 +0200 [thread overview]
Message-ID: <CAEwRq=pNqK+cE+Vq6DxPgT9FCg=4kmsno5D8vSfjM7Fsg5FZLA@mail.gmail.com> (raw)
In-Reply-To: <87eet8v948.fsf@gnu.org>
Hello,
thanks for the help, but...
On Tue, Mar 31, 2020 at 5:26 PM Ludovic Courtès <ludo@gnu.org> wrote:
> I was proposing a custom action for the Shepherd service, just like the
> mcron Shepherd service has a custom ‘schedule’ action that one can
> invoke with “herd schedule mcron”.
>
> Hope that’s clearer!
I've found the shepherd-schedule-action code, but that does not tell me
how to implement the whole thing.
Let me try harder, the following are all questions.
I do not know if they make any sense at all...
How do I make the running daemon use a proxy ?
By doing setenv() calls in builtins.cc builtinDownload()
before the execv(guix perform-download) ?
How do I make the running daemon know which proxy to use ?
By getting it from the settings object from globals.hh ?
How do I make the running daemon change the value stored
in the settings object ?
By sending it an order to do so via the listening socket ?
What will send this order through that socket ?
Another, one-shot, ephemeral, guix-daemon process with
the --set-proxy command-line option ?
What is the UI to run that guix-daemon --set-proxy ?
Use herd set-proxy guix-daemon "https://proxy:3128" ?
(Like what is done for mcron)
I really need a few "make this thing here do that" hints...
And then also a bit of a hint on how I would test the
modifications without risking my running system.
I hope that's not too demanding...
Thanks
--
Vincent Legoll
next prev parent reply other threads:[~2020-04-03 22:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 10:04 Proxy settings wrt guix daemon Vincent Legoll
2020-03-29 15:00 ` Ludovic Courtès
2020-03-30 12:07 ` Vincent Legoll
2020-03-31 15:26 ` Ludovic Courtès
2020-04-03 22:29 ` Vincent Legoll [this message]
2020-04-04 15:31 ` Mathieu Othacehe
2020-04-06 8:57 ` Ludovic Courtès
2020-04-06 9:13 ` Vincent Legoll
2020-04-07 9:38 ` Ludovic Courtès
2020-04-07 10:07 ` Vincent Legoll
2020-04-07 10:39 ` Ludovic Courtès
2020-04-07 16:47 ` Mathieu Othacehe
2020-04-07 16:54 ` Mathieu Othacehe
2020-04-07 20:12 ` Ludovic Courtès
2020-04-07 20:10 ` Ludovic Courtès
2020-04-07 20:14 ` Ludovic Courtès
2020-04-08 8:27 ` Mathieu Othacehe
2020-04-08 10:44 ` Ludovic Courtès
2020-04-10 13:26 ` Danny Milosavljevic
2020-04-10 14:40 ` Ludovic Courtès
2020-04-10 14:42 ` Vincent Legoll
2020-04-10 18:47 ` Danny Milosavljevic
2020-04-10 22:44 ` 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
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='CAEwRq=pNqK+cE+Vq6DxPgT9FCg=4kmsno5D8vSfjM7Fsg5FZLA@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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 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).