cpud did not connect for more than 100ms #85

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!):

2022/04/11 16:42:32 CPUD:namespace is ""
2022/04/11 09:42:32 cpud did not connect for more than 100ms

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:

CPU_NAMESPACE="" ./cpu

i get:

2022/04/11 16:53:48 CPUD:namespace is "/lib:/lib64:/usr:/bin:/etc:/home"

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:

_, wantNameSpace := os.LookupEnv("CPU_NAMESPACE")