consider

 http://golang.org/src/pkg/net/rpc/client.go#L164

this prints to stderr in case of error, and there is no way to suppress this. 

In my scenario, a command-line program serves RPC to a daemon, and it is normal for the
command line program to be interrupted with ^C . When this happens, I get spurious error
output, eg.  

2013/09/11 17:52:48 rpc: client protocol error: unexpected EOF
2013/09/11 17:52:48 rpc: writing response: write unix : broken pipe

How about a 

  rpc.SetLog(interface { Println(interface{}...)})

method to control the RPC logging?

This is with Linux gc,

 changeset:   17988:a71616f65cb1