-
Notifications
You must be signed in to change notification settings - Fork 28
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
cpud did not connect for more than 100ms #85
Comments
Yea, CPU_NAMESPACE has been redesigned a bit:
Regarding the timeout: Try increasing it; i.e., |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
if you set cpu -namespace "" (empty string), instead of none or ":", cpu will complain.
notably debug lines (target machine is 7 hours ahead, which helps with debugging!):
looks like cpu started the 9p server, but cpud never dialed back. there's a mismatch in what it means to have no CPU_NAMESPACE (empty vs non-existent). cpu will start the 9p server since namespace is not "none". cpud won't dial back since len(bindover) == 0.
possibly related: should CPU_NAMESPACE work for cpu?
if i try this:
i get:
not sure if CPU_NAMESPACE is used in cpu anymore. its value gets discarded in one of the spots i see in cmds/cpu/cpu.go:
The text was updated successfully, but these errors were encountered: