From: Brice Waegeneire <brice@waegenei.re>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 41238@debbugs.gnu.org
Subject: bug#41238: guix deploy close ssh session after each store items sent
Date: Fri, 15 May 2020 07:46:25 +0000 [thread overview]
Message-ID: <b5800a12136c40aa3311d32b053684d5@waegenei.re> (raw)
In-Reply-To: <87wo5du1id.fsf@gmail.com>
On 2020-05-15 06:59, Oleg Pykhalov wrote:
> Brice Waegeneire <brice@waegenei.re> writes:
>
>> “guix deploy” bugs; they keep coming! “guix deploy” doesn't make use
>> of SSH
>> channels[0], instead it close the SSH session each time after sending
>> store
>> items.
>
> Did you try a built in SSH's “Control*” feature?
>
> ssh_config (0)
>
> ControlMaster auto
> ControlPath ~/.ssh/master-%r@%h:%p
> ControlPersist yes
Of course, it's my default setting for SSH (and the host I tried to
deploy
to). But “guix deploy” don't support it; it's the core of the issue
here.
I didn't mention those options in the initial bug report because IFAIK
the
ssh functionality for “guix deploy” is provided by guile-ssh, a wrapper
around libssh which isn't related to OpenSSH in any way. So the
“Control*”
options doesn't apply here, instead they talk about channels and
session[0]
which seems to be the terms used in the SSH specification.
[0]: https://api.libssh.org/stable/libssh_tutor_guided_tour.html
next prev parent reply other threads:[~2020-05-15 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 16:32 bug#41238: guix deploy close ssh session after each store items sent Brice Waegeneire
2020-05-15 6:59 ` Oleg Pykhalov
2020-05-15 7:46 ` Brice Waegeneire [this message]
2022-01-18 7:08 ` Brice Waegeneire
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=b5800a12136c40aa3311d32b053684d5@waegenei.re \
--to=brice@waegenei.re \
--cc=41238@debbugs.gnu.org \
--cc=go.wigust@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 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.