Hello,
I think this is working as intended.
When you "kill -9", that is sending the SIGKILL signal -- you are asking
the program to shut down *uncleanly* and immediately. The mosh-client
dies immediately, and it doesn't have a chance to let the server know
that it won't be coming back. The server has no way to distinguish this
from a case where the client simply lost its network connection (but
might regain it later).
Please use a nicer signal to kill the mosh-client. (E.g. the default for
"kill", or just exit from within the client.) Then it will have a chance
to shut down the connection cleanly.
(You might still have the problem if you exit the client while it
doesn't have a network connection -- then it again doesn't have a chance
to let the server know that it's quitting. But that is a different
problem that is hard to escape given mosh's design of everlasting,
roamable connections.)
** Changed in: mosh (Ubuntu)
Assignee: (unassigned) => Keith Winstein (keithw)
** Also affects: mosh
Importance: Undecided
Status: New
** Changed in: mosh
Assignee: (unassigned) => Keith Winstein (keithw)
** Changed in: mosh (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446982
Title:
Wrong kill mode on shutdown
To manage notifications about this bug go to:
https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
