all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>,
	Artyom Poptsov <poptsov.artyom@gmail.com>
Cc: 30522-done@debbugs.gnu.org
Subject: bug#30522: Guile-SSH retries upon “guile --listen” failure to start
Date: Wed, 21 Feb 2018 23:07:44 +0100	[thread overview]
Message-ID: <87o9kic7yn.fsf_-_@gnu.org> (raw)
In-Reply-To: <87sh9vbm7k.fsf@fastmail.com> (Marius Bakke's message of "Tue, 20 Feb 2018 18:33:03 +0100")

Hello Artyom & Marius,

Marius Bakke <mbakke@fastmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>>> It would still be good with a better failure mode, but I'll file this
>>> under "pebkac" for now.
>>
>> Yes, I’m surprised it ended up looping.  Did you try to strace it or
>> something to see what was going on?  Perhaps guile failed to start
>> altogether and Guile-SSH kept retrying?
>
> Indeed.  Guile-SSH kept trying to start `guile --listen` over and over.

Artyom, do you think we could arrange for Guile-SSH to properly detect
failure to start ‘guile --listen’ and report it instead of retrying?

Perhaps it could check the exit code of ‘guile --listen’ and distinguish
127 (“command not found”) from other exit codes?

(For more context, see <https://bugs.gnu.org/30522>.)

Thanks,
Ludo’.

  reply	other threads:[~2018-02-21 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 13:48 bug#30522: offloading requires guile-readline on the remote system Marius Bakke
2018-02-19 15:35 ` Ludovic Courtès
2018-02-19 16:11   ` Marius Bakke
2018-02-19 20:31     ` Ludovic Courtès
2018-02-20 17:33       ` Marius Bakke
2018-02-21 22:07         ` Ludovic Courtès [this message]
2018-02-24 10:52           ` bug#30522: Guile-SSH retries upon “guile --listen” failure to start Artyom Poptsov
2018-03-05  2:15             ` Artyom Poptsov
2018-03-05 10:11               ` 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=87o9kic7yn.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=30522-done@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    --cc=poptsov.artyom@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.