f3a05eb800
Some warnings about go1.16 compatibility, so including them here: + go mod tidy -modfile=vendor.mod github.com/docker/cli/cli/registry/client imports github.com/docker/distribution/registry/api/v2 imports github.com/gorilla/mux loaded from github.com/gorilla/mux@v1.7.0, but go 1.16 would select v1.8.0 github.com/docker/cli/cli/compose/loader imports gopkg.in/yaml.v2 tested by gopkg.in/yaml.v2.test imports gopkg.in/check.v1 loaded from gopkg.in/check.v1@v1.0.0-20200227125254-8fa46927fb4f, but go 1.16 would select v1.0.0-20201130134442-10cb98267c6c github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/Shopify/logrus-bugsnag loaded from github.com/Shopify/logrus-bugsnag@v0.0.0-20170309145241-6dbc35f2c30d, but go 1.16 would select v0.0.0-20171204204709-577dee27f20d github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server/storage imports gopkg.in/rethinkdb/rethinkdb-go.v6 imports github.com/opentracing/opentracing-go loaded from github.com/opentracing/opentracing-go@v1.1.0, but go 1.16 would select v1.2.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server/storage imports gopkg.in/rethinkdb/rethinkdb-go.v6 imports github.com/opentracing/opentracing-go/ext loaded from github.com/opentracing/opentracing-go@v1.1.0, but go 1.16 would select v1.2.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server/storage imports gopkg.in/rethinkdb/rethinkdb-go.v6 imports github.com/opentracing/opentracing-go/log loaded from github.com/opentracing/opentracing-go@v1.1.0, but go 1.16 would select v1.2.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/afero loaded from github.com/spf13/afero@v1.1.2, but go 1.16 would select v1.2.2 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/cast loaded from github.com/spf13/cast@v1.3.0, but go 1.16 would select v1.3.1 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/jwalterweatherman loaded from github.com/spf13/jwalterweatherman@v1.0.0, but go 1.16 would select v1.1.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports gopkg.in/ini.v1 loaded from gopkg.in/ini.v1@v1.51.0, but go 1.16 would select v1.56.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/afero imports github.com/spf13/afero/mem loaded from github.com/spf13/afero@v1.1.2, but go 1.16 would select v1.2.2 To upgrade to the versions selected by go 1.16: go mod tidy -go=1.16 && go mod tidy -go=1.17 If reproducibility with go 1.16 is not needed: go mod tidy -compat=1.17 For other options, see: https://golang.org/doc/modules/pruning Signed-off-by: Sebastiaan van Stijn <github@gone.nl> |
||
---|---|---|
.. | ||
internal | ||
.gitignore | ||
.golangci.yml | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
MAINTAINERS.md | ||
Makefile | ||
Makefile.common | ||
NOTICE | ||
README.md | ||
SECURITY.md | ||
arp.go | ||
buddyinfo.go | ||
cmdline.go | ||
cpuinfo.go | ||
cpuinfo_armx.go | ||
cpuinfo_mipsx.go | ||
cpuinfo_others.go | ||
cpuinfo_ppcx.go | ||
cpuinfo_riscvx.go | ||
cpuinfo_s390x.go | ||
cpuinfo_x86.go | ||
crypto.go | ||
doc.go | ||
fixtures.ttar | ||
fs.go | ||
fscache.go | ||
ipvs.go | ||
kernel_random.go | ||
loadavg.go | ||
mdstat.go | ||
meminfo.go | ||
mountinfo.go | ||
mountstats.go | ||
net_conntrackstat.go | ||
net_dev.go | ||
net_ip_socket.go | ||
net_protocols.go | ||
net_sockstat.go | ||
net_softnet.go | ||
net_tcp.go | ||
net_udp.go | ||
net_unix.go | ||
netstat.go | ||
proc.go | ||
proc_cgroup.go | ||
proc_environ.go | ||
proc_fdinfo.go | ||
proc_io.go | ||
proc_limits.go | ||
proc_maps.go | ||
proc_ns.go | ||
proc_psi.go | ||
proc_smaps.go | ||
proc_stat.go | ||
proc_status.go | ||
schedstat.go | ||
slab.go | ||
stat.go | ||
swaps.go | ||
ttar | ||
vm.go | ||
xfrm.go | ||
zoneinfo.go |
README.md
procfs
This package provides functions to retrieve system, kernel, and process metrics from the pseudo-filesystems /proc and /sys.
WARNING: This package is a work in progress. Its API may still break in backwards-incompatible ways without warnings. Use it at your own risk.
Usage
The procfs library is organized by packages based on whether the gathered data is coming from
/proc, /sys, or both. Each package contains an FS
type which represents the path to either /proc,
/sys, or both. For example, cpu statistics are gathered from
/proc/stat
and are available via the root procfs package. First, the proc filesystem mount
point is initialized, and then the stat information is read.
fs, err := procfs.NewFS("/proc")
stats, err := fs.Stat()
Some sub-packages such as blockdevice
, require access to both the proc and sys filesystems.
fs, err := blockdevice.NewFS("/proc", "/sys")
stats, err := fs.ProcDiskstats()
Package Organization
The packages in this project are organized according to (1) whether the data comes from the /proc
or
/sys
filesystem and (2) the type of information being retrieved. For example, most process information
can be gathered from the functions in the root procfs
package. Information about block devices such as disk drives
is available in the blockdevices
sub-package.
Building and Testing
The procfs library is intended to be built as part of another application, so there are no distributable binaries.
However, most of the API includes unit tests which can be run with make test
.
Updating Test Fixtures
The procfs library includes a set of test fixtures which include many example files from
the /proc
and /sys
filesystems. These fixtures are included as a ttar file
which is extracted automatically during testing. To add/update the test fixtures, first
ensure the fixtures
directory is up to date by removing the existing directory and then
extracting the ttar file using make fixtures/.unpacked
or just make test
.
rm -rf fixtures
make test
Next, make the required changes to the extracted files in the fixtures
directory. When
the changes are complete, run make update_fixtures
to create a new fixtures.ttar
file
based on the updated fixtures
directory. And finally, verify the changes using
git diff fixtures.ttar
.