You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make control sessions work on the reattach path too
et reaches a live session two ways: bootstrapping a new one over SSH,
and reattaching to one already saved under --name. Only the first ran
the control listener, so a control session whose client had died was
reattached and then immediately killed: the reattach path builds a
terminal console and calls run() with noexit unset, which appends
'; exit'.
Hoist console creation and control-socket setup above the branch, and
give both paths one driver. A control session now behaves the same
however it got there.
Move the live control files (socket, session-end note) to ~/.et/control
rather than sharing ~/.et/sessions with the saved records. Sharing one
flat directory reads well until a name collides: a session may legally
be named 'foo.sock', which is exactly the path session 'foo' wants for
its socket, and a listing cannot tell the two apart without reserving
suffixes from the session namespace. A sibling directory leaves that
namespace entirely to SessionStore, which is unmodified.
0 commit comments