Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sockets flush does not stop mux process #278

Open
jsimonetti opened this issue Jun 5, 2018 · 0 comments · May be fixed by #461
Open

sockets flush does not stop mux process #278

jsimonetti opened this issue Jun 5, 2018 · 0 comments · May be fixed by #461
Projects

Comments

@jsimonetti
Copy link

After logging in to server a mux process and assh connect process is started:

% ps faux | grep server
jeroen 31863  0.1  0.0 532640  8008 pts/1    Sl   01:11   0:00  \_ /usr/bin/assh connect --port=22 server
jeroen 31895  0.0  0.0  40784  2564 ?        Ss   01:11   0:00  \_ ssh: /home/jsimonetti/.ssh/cm/server-22-jeroen.sock [mux]
% assh sockets list
1 active control sockets in "~/.ssh/cm/%h-%p-%r.sock":

- server-22-jeroen.sock (19 seconds)

However, when flushin the sockets, the mux process and assh connect process is still running:

% assh sockets flush
Closed 1 control sockets.
% ps faux | grep server
jeroen 31863  0.0  0.0 532640  8008 pts/1    Sl   01:11   0:00  \_ /usr/bin/assh connect --port=22 server
jeroen 31895  0.0  0.0  40784  2564 ?        Ss   01:11   0:00  \_ ssh: /home/jsimonetti/.ssh/cm/server-22-jeroen.sock [mux]
% 

It would be nice if those processes could be killed when flushing sockets.

@moul moul added this to Triage in Kanban Jun 7, 2020
@chanchal1987 chanchal1987 linked a pull request Nov 24, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Kanban
  
Triage
Development

Successfully merging a pull request may close this issue.

1 participant