zeldon
/
htop
mirror of https://github.com/xzeldon/htop.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
htop/unsupported/UnsupportedProcessList.h

20 lines
520 B
C
Raw Normal View History

Files moved and added for supporting separate platforms.
2014-11-24 20:55:49 +00:00
#ifndef HEADER_UnsupportedProcessList
#define HEADER_UnsupportedProcessList
/*
htop - UnsupportedProcessList.h
(C) 2014 Hisham H. Muhammad
Update License consistently to GPLv2 as per COPYING file
2020-10-05 07:51:32 +00:00
Released under the GNU GPLv2, see the COPYING file
Files moved and added for supporting separate platforms.
2014-11-24 20:55:49 +00:00
in the source distribution for its full text.
*/
Unsupported: pass compilation
2021-01-28 17:19:38 +00:00
#include "ProcessList.h"
Add a new DynamicMeter class for runtime Meter extension This commit is based on exploratory work by Sohaib Mohamed. The end goal is two-fold - to support addition of Meters we build via configuration files for both the PCP platform and for scripts ( https://github.com/htop-dev/htop/issues/526 ) Here, we focus on generic code and the PCP support. A new class DynamicMeter is introduced - it uses the special case 'param' field handling that previously was used only by the CPUMeter, such that every runtime-configured Meter is given a unique identifier. Unlike with the CPUMeter this is used internally only. When reading/writing to htoprc instead of CPU(N) - where N is an integer param (CPU number) - we use the string name for each meter. For example, if we have a configuration for a DynamicMeter for some Redis metrics, we might read and write "Dynamic(redis)". This identifier is subsequently matched (back) up to the configuration file so we're able to re-create arbitrary user configurations. The PCP platform configuration file format is fairly simple. We expand configs from several directories, including the users homedir alongside htoprc (below htop/meters/) and also /etc/pcp/htop/meters. The format will be described via a new pcp-htop(5) man page, but its basically ini-style and each Meter has one or more metric expressions associated, as well as specifications for labels, color and so on via a dot separated notation for individual metrics within the Meter. A few initial sample configuration files are provided below ./pcp/meters that give the general idea. The PCP "derived" metric specification - see pmRegisterDerived(3) - is used as the syntax for specifying metrics in PCP DynamicMeters.
2021-06-23 07:44:56 +00:00
ProcessList* ProcessList_new(UsersTable* usersTable, Hashtable* dynamicMeters, Hashtable* pidMatchList, uid_t userId);
Files moved and added for supporting separate platforms.
2014-11-24 20:55:49 +00:00
Add ProcessList_delete to the variable interface.
2014-11-27 19:48:38 +00:00
void ProcessList_delete(ProcessList* this);
Continue to update generic data in paused mode Generic data, as CPU and memory usage, are used by Meters. In paused mode they would stop receiving updates and especially Graph Meters would stop showing continuous data. Improves: #214 Closes: #253
2020-10-13 14:03:37 +00:00
void ProcessList_goThroughEntries(ProcessList* super, bool pauseProcessUpdate);
Make unsupported run
2015-07-12 16:26:33 +00:00
Files moved and added for supporting separate platforms.
2014-11-24 20:55:49 +00:00
#endif