Little helper to run CNCF's k3s in Docker
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
k3d/vendor/github.com/prometheus/procfs
Batuhan Apaydın f59216c2e0 docker context support 3 years ago
..
internal/fs docker context support 3 years ago
.gitignore docker context support 3 years ago
.golangci.yml docker context support 3 years ago
CONTRIBUTING.md docker context support 3 years ago
LICENSE docker context support 3 years ago
MAINTAINERS.md docker context support 3 years ago
Makefile docker context support 3 years ago
Makefile.common docker context support 3 years ago
NOTICE docker context support 3 years ago
README.md docker context support 3 years ago
buddyinfo.go docker context support 3 years ago
doc.go docker context support 3 years ago
fixtures.ttar docker context support 3 years ago
fs.go docker context support 3 years ago
go.mod docker context support 3 years ago
go.sum docker context support 3 years ago
ipvs.go docker context support 3 years ago
mdstat.go docker context support 3 years ago
mountinfo.go docker context support 3 years ago
mountstats.go docker context support 3 years ago
net_dev.go docker context support 3 years ago
net_unix.go docker context support 3 years ago
proc.go docker context support 3 years ago
proc_environ.go docker context support 3 years ago
proc_io.go docker context support 3 years ago
proc_limits.go docker context support 3 years ago
proc_ns.go docker context support 3 years ago
proc_psi.go docker context support 3 years ago
proc_stat.go docker context support 3 years ago
proc_status.go docker context support 3 years ago
stat.go docker context support 3 years ago
ttar docker context support 3 years ago
xfrm.go docker context support 3 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.