summaryrefslogtreecommitdiff
path: root/open_issues
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2018-09-03 17:20:33 +0200
committerThomas Schwinge <thomas@codesourcery.com>2018-09-03 17:20:33 +0200
commite089958182566e2076ecf724dd2871edf287dcfa (patch)
tree721e3baf31b5acef3352d3383a62968857d2f3f2 /open_issues
parentcf42fa246bc194de6bc1d366ef161692e40643b7 (diff)
SSH: PTY allocation request failed
Diffstat (limited to 'open_issues')
-rw-r--r--open_issues/ssh_pty_allocation_request_failed.mdwn31
1 files changed, 31 insertions, 0 deletions
diff --git a/open_issues/ssh_pty_allocation_request_failed.mdwn b/open_issues/ssh_pty_allocation_request_failed.mdwn
new file mode 100644
index 00000000..af9e7135
--- /dev/null
+++ b/open_issues/ssh_pty_allocation_request_failed.mdwn
@@ -0,0 +1,31 @@
+[[!meta copyright="Copyright © 2018 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!meta title="SSH: PTY allocation request failed"]]
+
+Occasionally seen when `ssh`ing to a Hurd system:
+
+ $ ssh [...]
+ PTY allocation request failed on channel 0
+ GNU laplace 0.9 GNU-Mach 1.8+git20180218-486-dbg/Hurd-0.9 i686-AT386
+ This is the GNU Hurd. Welcome. [...]
+ [No prompt displayed.]
+ [C-d]
+ Connection to [...] closed.
+
+That is, we failed to get a PTY allocated.
+
+We currently set up a limited number of translator nodes providing preallocated
+PTYs ([[hurd/translator/term]] translator instances), instead of dynamically
+allocating via `/dev/ptmx`, for example.
+(Which might or might not resolve this issue; there might be some resource leak
+involved?)
+
+Last seen timestamp: 2018-07 (lost exact date).