On Thu, Apr 27, 2017 at 08:55:36AM -0700, Chris Hopkins wrote: > What's the current thinking on this sort of error handling? It's hard to > say "Handle errors properly" when the standard library is butchering the > original error message.
This most likely *is* the original error, as returned by your system. It corresponds to the EHOSTDOWN error code and was apparently encountered during a write system call. The system call interface on Unix just doesn't give you any more than this. You need to look up the conditions under which your system might return that particular error code. If you really think the message is bogus, you might want to compare the errno-to-errstr mapping in package syscall against your local system headers. This is going to depend on OS and arch, of course. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
