The os/user package nowadays says:
When cgo is available, and the required routines are implemented
in libc for a particular platform, cgo-based (libc-backed) code
is used. This can be overridden by using osusergo build tag,
which enforces the pure Go implementation.
So we don't need to work around it anymore.
Signed-off-by: Brad Fitzpatrick <brad@danga.com>
- correct logging that logged functions instead of their value
- use ID vs Id naming
- use correct function names in comments
Change-Id: I61562cef7ebac7337ec6c85312cdf7915cb1a84b
Brad Fitzpatrick