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

[tether] make SSH server loop more resilient #2626

Open
caglar10ur opened this issue Oct 9, 2016 · 3 comments
Open

[tether] make SSH server loop more resilient #2626

caglar10ur opened this issue Oct 9, 2016 · 3 comments
Labels
component/tether kind/debt Problems that increase the cost of other work kind/enhancement Behavior that was intended, but we want to make better priority/p4

Comments

@caglar10ur
Copy link
Contributor

Otherwise we may end up in with high cpu usage (#2584 (comment))

@caglar10ur caglar10ur added kind/enhancement Behavior that was intended, but we want to make better component/tether labels Oct 9, 2016
@caglar10ur caglar10ur self-assigned this Oct 9, 2016
@hickeng
Copy link
Member

hickeng commented Oct 9, 2016

Also the raciness aspect of the t.conn handling in the !t.testing block.

@mdubya66 mdubya66 added this to the VIC GA Release milestone Oct 9, 2016
@mdubya66 mdubya66 removed this from the VIC GA Release milestone Oct 24, 2016
@hmahmood hmahmood added the kind/debt Problems that increase the cost of other work label Apr 12, 2017
@hickeng
Copy link
Member

hickeng commented Apr 13, 2017

@caglar10ur has this been addressed by the exec/attach changes? #4339

@caglar10ur
Copy link
Contributor Author

no, not really. It should be addressed with the tether re-org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/tether kind/debt Problems that increase the cost of other work kind/enhancement Behavior that was intended, but we want to make better priority/p4
Projects
None yet
Development

No branches or pull requests

4 participants