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.

Sign up for GitHub

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

Jump to bottom

sockets flush does not stop mux process #278

Open

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

jsimonetti commented Jun 5, 2018

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.

The text was updated successfully, but these errors were encountered:

chanchal1987 linked a pull request

that will close this issue

fix: stop mux process on sockets flux #461

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment