Home
last modified time | relevance | path

Searched refs:cgroups (Results 1 – 14 of 14) sorted by relevance

/systemd-251/src/shared/
Dbus-unit-procs.c27 static int add_cgroup(Hashmap *cgroups, const char *path, bool is_const, struct CGroupInfo **ret) { in add_cgroup() argument
31 assert(cgroups); in add_cgroup()
36 cg = hashmap_get(cgroups, path); in add_cgroup()
51 r = add_cgroup(cgroups, pp, false, &parent); in add_cgroup()
73 r = hashmap_put(cgroups, cg->cgroup_path, cg); in add_cgroup()
91 Hashmap *cgroups, in add_process() argument
99 assert(cgroups); in add_process()
103 r = add_cgroup(cgroups, path, true, &cg); in add_process()
110 static void remove_cgroup(Hashmap *cgroups, struct CGroupInfo *cg) { in remove_cgroup() argument
111 assert(cgroups); in remove_cgroup()
[all …]
/systemd-251/docs/
DCGROUP_DELEGATION.md14 control groups (cgroups) a bit and are trying to integrate your software with
37 with cgroups and systemd, in particular as they shine more light on the various
48 to have processes directly attached to a cgroup that also has child cgroups and
51 node then it may not have child cgroups. (Note that there are some minor
57 writer, i.e. a single process managing it. It's OK if different cgroups have
64 your container manager creates and manages cgroups in the system's root cgroup
88 systemd supports three different modes how cgroups are set up. Specifically:
140 The low-level kernel cgroups feature is exposed in systemd in three different
144 processes systemd itself starts. Units of these types have cgroups that are
197 Container managers and suchlike often want to control cgroups directly using
[all …]
/systemd-251/src/oom/
Doomd-manager.c47 JsonVariant *c, *cgroups; in process_managed_oom_message() local
61 cgroups = json_variant_by_key(parameters, "cgroups"); in process_managed_oom_message()
62 if (!cgroups) in process_managed_oom_message()
66 JSON_VARIANT_ARRAY_FOREACH(c, cgroups) { in process_managed_oom_message()
/systemd-251/shell-completion/zsh/
D_systemd31 ':cgroups:(cpuset cpu cpuacct memory devices freezer blkio)'
/systemd-251/catalog/
Dsystemd.fr.catalog.in342 - "cgroups-missing" — le noyau a été compilé sans le support des groupes
343 de contrôle (cgroups) ou l'accès aux fichiers d'interface est restreint
Dsystemd.ru.catalog.in393 - "cgroups-missing" — ядро собрано без поддержки контрольных групп, либо
Dsystemd.pl.catalog.in401 • „cgroups-missing” — jądro zostało skompilowane bez obsługi cgroups
Dsystemd.it.catalog.in407 - "cgroups-missing" — il kernel era compilato senza supporto cgroup o l'accesso ai
Dsystemd.catalog.in404 - "cgroups-missing" — the kernel was compiled without cgroup support or access
/systemd-251/test/fuzz/fuzz-catalog/
Dsystemd.pl.catalog381 • „cgroups-missing” — jądro zostało skompilowane bez obsługi cgroups
/systemd-251/
DREADME383 kernel (taint flag 'cgroups-missing'), the system is using the old
DTODO51 - dynamic resource management with cgroups
394 * automatically ignore threaded cgroups in cg_xyz().
893 * cgroups: use inotify to get notified when somebody else modifies cgroups
1004 * beef up pam_systemd to take unit file settings such as cgroups properties as
1200 * cgroups:
Dmeson.build251 conf.set_quoted('SYSTEMD_CGROUPS_AGENT_PATH', rootlibexecdir / 'systemd-cgroups-age…
3297 'systemd-cgroups-agent',
3298 'src/cgroups-agent/cgroups-agent.c',
DNEWS251 cgroups are used in addition to trusted.delegate and
4128 * Support for the cpuset cgroups v2 controller has been added.
6056 * New documentation has been added to document cgroups delegation,
7124 compatibility with "legacy" cgroups-v1 setups. Specifically, the
7127 cgroups-v1 hierarchy), the only externally visible change being that
7128 the cgroups-v2 hierarchy is also mounted, to
7130 compatibility with "legacy" cgroups-v1, while taking benefit of the
7131 better management capabilities of cgroups-v2.
7139 (i.e. the cgroups-v1 + cgroups-v2 mixture discussed above) now, but
7141 cgroups-v2 mode). The third option for the compile time option is
[all …]