Mirror of the HTOP dev team main htop repository - Mirror of the git repository for htop from Github

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update license headers to explicitly say GPLv2+	Daniel Lange	2021-09-22	1	-1/+1
\|
*	Add columns for process autogroup identifier and nice value	Nathan Scott	2021-08-09	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \|	Adds AGRP (autogroup) and ANI (autogroup nice) columns that report the information from /proc/PID/autogroup, as well as handlers for '{' and '}' to change the autogroup nice value. This is guarded by /proc/sys/kernel/sched_autogroup_enabled such that sampling and/or changing values wont be attempted unless the kernel feature is enabled. Fixes: #720
*	Update the PCP platform to use common Process fields and code	Nathan Scott	2021-06-09	1	-1/+2
\| \| \| \| \| \| \|	Remove code now that we have common platform-independent command line wrangling (thanks BenBE!). Add PCP platform support for a handful of other recently arriving odds and ends - ELAPSED time, CWD, and so on.
*	Add a platform for Performance Co-Pilot (PCP) metrics	Nathan Scott	2021-06-09	1	-0/+50
	This introduces an initial platform for extracting metrics using the PCP performance metrics API - PMAPI(3). It can be used via the --enable-pcp=yes configure option. So far I've added support for live localhost metrics only, and only using pre-defined metrics already found in htop. If available, all sampling is performed by pmcd(1) - else, we fallback to htop doing the metric sampling itself (all below the PMAPI). When pmcd is used, it may be configured to run children with elevated privileges, so htop does not need to be setuid (authentication with pmcd is available). Additionally, the PMAPI allows us to support archives (for historical analysis and for automated regression tests in htop). We'll need platform-specific command line argument additions, which isn't yet feasible in htop (not difficult to add though). The goal of this first version is minimal impact in terms of modifying the htop codebase, to introduce key ideas in PCP (metric namespace, metadata, APIs and so on) and give us something to discuss, experiment with and build on.