installion cannot be cancelled

  • Open
  • quality assurance status badge
Details
3 participants
  • Ludovic Courtès
  • Mathieu Othacehe
  • Ricardo Wurmus
Owner
unassigned
Submitted by
Ricardo Wurmus
Severity
normal
R
R
Ricardo Wurmus wrote on 21 Dec 2019 22:42
(address . bug-guix@gnu.org)
87fthdpd8o.fsf@elephly.net
When I first tried to install one of the new build servers for
ci.guix.gnu.org I forgot that the firewall rules prevent these servers
from accessing ci.guix.gnu.org via its public IP address. I started the
installation process and waited …

When I realized that I had to first add the internal IP to /etc/hosts I
decided to cancel the installation, but no matter from what angle I hit
Ctrl-C or Ctrl-Z I could not abort the installation — which I hope
would have eventually timed out.

--
Ricardo
L
L
Ludovic Courtès wrote on 30 Dec 2019 19:42
(name . Ricardo Wurmus)(address . rekado@elephly.net)
877e2d7j0d.fsf@gnu.org
Hi,

Ricardo Wurmus <rekado@elephly.net> skribis:

Toggle quote (10 lines)
> When I first tried to install one of the new build servers for
> ci.guix.gnu.org I forgot that the firewall rules prevent these servers
> from accessing ci.guix.gnu.org via its public IP address. I started the
> installation process and waited …
>
> When I realized that I had to first add the internal IP to /etc/hosts I
> decided to cancel the installation, but no matter from what angle I hit
> Ctrl-C or Ctrl-Z I could not abort the installation — which I hope
> would have eventually timed out.

You mean that Ctrl-C wouldn’t work on the ‘guix system init’ process,
right? Is that behavior controlled by Newt, Mathieu?

Thanks,
Ludo’.
M
M
Mathieu Othacehe wrote on 31 Dec 2019 12:10
(name . Ludovic Courtès)(address . ludo@gnu.org)
87h81gsqco.fsf@gmail.com
Hello,

Toggle quote (3 lines)
> You mean that Ctrl-C wouldn’t work on the ‘guix system init’ process,
> right? Is that behavior controlled by Newt, Mathieu?

Before running the guix process, newt is suspended and resumed right
after (see run-install-shell procedure). So it should reset the original
terminal settings. Maybe it doesn't, or it's an issue with kmscon.

I'll try to investigate.

Thanks,

Mathieu
?