Searched refs:release_agent (Results 1 – 4 of 4) sorted by relevance
242 - release_agent: the path to use for release notifications (this file289 of the "release_agent" file in that hierarchy's root directory,296 a cgroup hierarchy's release_agent path is empty.373 release_agent. Rebinding is hardly useful as it only works when the374 hierarchy is empty and release_agent itself should be replaced with378 To Specify a hierarchy's release_agent:379 # mount -t cgroup -o cpuset,release_agent="/sbin/cpuset_release_agent" \382 Note that specifying 'release_agent' more than once will return failure.393 If you want to change the value of release_agent:394 # echo "/sbin/new_release_agent" > /sys/fs/cgroup/rg1/release_agent
254 currently provides release_agent for it; unfortunately, this mechanism258 specified as the release_agent. This is a long deprecated method of287 In unified hierarchy, the release_agent mechanism is no longer288 supported and the interface files "release_agent" and
779 echo "/sbin/cpuset_release_agent" > /sys/fs/cgroup/cpuset/release_agent
1344 char *release_agent; member1401 if (opts->release_agent) in parse_cgroupfs_options()1403 opts->release_agent = in parse_cgroupfs_options()1405 if (!opts->release_agent) in parse_cgroupfs_options()1513 if (opts.subsys_mask != root->subsys_mask || opts.release_agent) in cgroup_remount()1541 if (opts.release_agent) { in cgroup_remount()1543 strcpy(root->release_agent_path, opts.release_agent); in cgroup_remount()1547 kfree(opts.release_agent); in cgroup_remount()1637 if (opts->release_agent) in init_cgroup_root()1638 strcpy(root->release_agent_path, opts->release_agent); in init_cgroup_root()[all …]