kubernetes/cmd/kube-proxy
Eric Paris 8e7d14196f Fix printing errors from failed binary runs
I had the kublet die on startup and the only error was "0x401da0"  Which
I assume is an address of the err.Error function.  The other way to fix
this, I think, would be to use err.Error(), however that could cause
fmt.Fprintf() problems, debuging on the error message people used.

Now I get a nice clean error I can understand:

"cAdvisor.New() err = mountpoint for cpu not found"
2015-04-10 17:56:47 -04:00
..
app Enable pprof on the kube-proxy's healthz http server. 2015-04-10 12:05:32 -07:00
proxy.go Fix printing errors from failed binary runs 2015-04-10 17:56:47 -04:00