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.
buildx/vendor/github.com/prometheus/procfs
ulyssessouza f2be09f4e4 Bump microsoft/hcsshim to v0.8.7
Signed-off-by: ulyssessouza <ulyssessouza@gmail.com>
5 years ago
..
internal Bump microsoft/hcsshim to v0.8.7 5 years ago
.gitignore vendor: initial vendor 6 years ago
.golangci.yml Bump moby/buildkit 5 years ago
CONTRIBUTING.md vendor: initial vendor 6 years ago
LICENSE vendor: initial vendor 6 years ago
MAINTAINERS.md Bump moby/buildkit 5 years ago
Makefile Bump moby/buildkit 5 years ago
Makefile.common Bump moby/buildkit 5 years ago
NOTICE vendor: initial vendor 6 years ago
README.md Bump moby/buildkit 5 years ago
arp.go Bump microsoft/hcsshim to v0.8.7 5 years ago
buddyinfo.go Bump microsoft/hcsshim to v0.8.7 5 years ago
cpuinfo.go Bump microsoft/hcsshim to v0.8.7 5 years ago
crypto.go Bump microsoft/hcsshim to v0.8.7 5 years ago
doc.go vendor: initial vendor 6 years ago
fixtures.ttar Bump microsoft/hcsshim to v0.8.7 5 years ago
fs.go Bump moby/buildkit 5 years ago
go.mod Bump moby/buildkit 5 years ago
go.sum Bump moby/buildkit 5 years ago
ipvs.go Bump moby/buildkit 5 years ago
mdstat.go Bump moby/buildkit 5 years ago
mountinfo.go Bump moby/buildkit 5 years ago
mountstats.go Bump moby/buildkit 5 years ago
net_dev.go Bump moby/buildkit 5 years ago
net_softnet.go Bump microsoft/hcsshim to v0.8.7 5 years ago
net_unix.go Bump moby/buildkit 5 years ago
proc.go Bump microsoft/hcsshim to v0.8.7 5 years ago
proc_environ.go Bump moby/buildkit 5 years ago
proc_fdinfo.go Bump microsoft/hcsshim to v0.8.7 5 years ago
proc_io.go Bump moby/buildkit 5 years ago
proc_limits.go Bump moby/buildkit 5 years ago
proc_ns.go Bump moby/buildkit 5 years ago
proc_psi.go Bump moby/buildkit 5 years ago
proc_stat.go Bump moby/buildkit 5 years ago
proc_status.go Bump microsoft/hcsshim to v0.8.7 5 years ago
schedstat.go Bump microsoft/hcsshim to v0.8.7 5 years ago
stat.go Bump moby/buildkit 5 years ago
ttar Bump moby/buildkit 5 years ago
vm.go Bump microsoft/hcsshim to v0.8.7 5 years ago
xfrm.go Bump moby/buildkit 5 years ago
zoneinfo.go Bump microsoft/hcsshim to v0.8.7 5 years ago

README.md

procfs

This procfs 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.

GoDoc Build Status Go Report Card

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, current 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()

Building and Testing

The procfs library is normally built as part of another application. However, when making changes to the library, the make test command can be used to run the API test suite.

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.