You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
gopsutil/cpu
Tobias Klauser ee12f66e4d cpu, v3/cpu: use sysconf package instead of exec'ing getconf
Currently, ClocksPerSec is determined by exec'ing getconf in func init,
i.e. on startup of every program importing the package. getconf might
not be present on some systems or is not executable by the current user.
To avoid this hard to control dependency, use the
github.com/tklauser/go-sysconf package which implements sysconf(3)
entirely in Go without cgo. The package is supported on all platforms
currently supported by the cpu and v3/cpu package of gopsutil.
4 years ago
..
testdata
cpu.go
cpu_darwin.go cpu, v3/cpu: use sysconf package instead of exec'ing getconf 4 years ago
cpu_darwin_cgo.go
cpu_darwin_nocgo.go
cpu_dragonfly.go cpu, v3/cpu: use sysconf package instead of exec'ing getconf 4 years ago
cpu_dragonfly_amd64.go
cpu_fallback.go
cpu_freebsd.go cpu, v3/cpu: use sysconf package instead of exec'ing getconf 4 years ago
cpu_freebsd_386.go
cpu_freebsd_amd64.go
cpu_freebsd_arm.go
cpu_freebsd_arm64.go
cpu_freebsd_test.go
cpu_linux.go cpu, v3/cpu: use sysconf package instead of exec'ing getconf 4 years ago
cpu_linux_test.go
cpu_openbsd.go cpu, v3/cpu: use sysconf package instead of exec'ing getconf 4 years ago
cpu_solaris.go cpu, v3/cpu: use sysconf package instead of exec'ing getconf 4 years ago
cpu_solaris_test.go
cpu_test.go
cpu_windows.go