Re: [systemd-devel] Fedora 25, cgroups V2 and systemd roadmap
Hello, Daniel, > We don't want to support out of tree kernel patches, This sounds very reasonable, I don't have anything against this policy. Still, I wonder: are you ruling out implementing "hybrid mode" (like Lennart uses in systemd) for libvirt? I mean a mode where you will use the 3 currently supported cgroup V2 controllers for libvirt (memory, io and pids; actually I don't know if you use the cgroups pids at all in libvirt, it is a new controller; BTW - do you ? ). And using other controllers (besides io, memory and pids) from cgroup V1 Regards, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Fedora 25, cgroups V2 and systemd roadmap
Hello, systemd developers, So we have now 3 V2 cgroups controller in the kernel (pids, memory and io). The CPU controller as of now is not merged in and is available only in an out of tree git repo (due to some debate over it with kernel scheduler developers). Not sure that it will be merged in the next 2 months. Fedora 25 is to be released in a month and a half, on 15 of November. https://fedoraproject.org/wiki/Releases/25/Schedule My questions are: what are the intentions regarding using cgroup v2 in systemd in F25 as the default instead of using cgroup V1? Is the absence of the CPU controller is a reason for not having cgroup V2 as a default in F25 ? and if so, why ? Regards, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Avoiding creating systemd memory and blkio controllers under /sys/fs/cgroup/memory and /sys/fs/cgroup/blkio.
Hi, Thank you for you quick response. I run Fedora 23 and made "dnf upgrade" today and rebooted. I have systemd-222-12.fc23.x86_64, and under /sys/fs/cgroup/memory and /sys/fs/cgroup/blkio/ I do see: system.slice and user.slice And there are some processes attached to subgroups: cat /sys/fs/cgroup/blkio/user.slice/user-0.slice/session-1.scope/tasks 852 973 cat /sys/fs/cgroup/blkio/user.slice/user-0.slice/session-4.scope/tasks 9913 9915 9916 10934 cat /sys/fs/cgroup/blkio/user.slice/user-0.slice/user@0.service/tasks 968 970 So my understanding is (please correct me if I am wrong) that this version is not high enough and not what you meant; in case it is so, from which systemd version is this supprted ? I am considering installing the latest RawHide Fedora for tests if it is include systemd which do not add all controllers to "delegation" scopes or services. Kevin On Sun, Jan 17, 2016 at 6:09 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Fri, 15.01.16 22:17, Kevin Wilson (wkev...@gmail.com) wrote: > >> Hi everyone, >> >> I had a Fedora 20 Machine (x86_64) on which I installed the >> latest 4.4 kernel released this week (I had built it from source). It >> had systemd 208. >> >> I wanted to test cgroup v2 (not in relation to systemd). In order to >> be able to activate >> cgoupv2 memory and cgroup controllers, the cgroup v1 controllers must >> be disabled. >> >> When I unmounted /sys/fs/cgroup/memory and /sys/fs/cgroup/blkio and mounted >> cgroup v2 on /testv2, cat /testv2/cgroup.controllers showed >> "memeory" and "io", and everything was fine. >> >> Then I installed Fedora 22 on this machine, and it has systemd 219. >> When I tried this >> same sequence, of unmounting /sys/fs/cgroup/memory and /sys/fs/cgroup/blkio >> and >> mounting cgroup v2 on /testv2, cat /testv2/cgroup.controllers showed nothing. >> >> Trying to add disabling cgroup memory controller, by adding >> cgroup_disable=memory, >> to the kernel command line caused the system to hang in boot (which is >> what I expected, >> but tried anyway...) >> >> Trying to solve the problem, I came to the conclusion that this is >> probably because >> there are processes in the memory and blkio groups which are held by >> systemd in F22, and which are not held in F20. >> >> On the F22, when I look under /sys/fs/cgouop/memory, I see >> >> /sys/fs/cgroup/memory/user.slice/ >> /sys/fs/cgroup/memory/user.slice/user-0.slice/ >> /sys/fs/cgroup/memory/user.slice/user-0.slice/session-10.scope >> /sys/fs/cgroup/memory/user.slice/user-0.slice/session-2.scope >> /sys/fs/cgroup/memory/user.slice/user-0.slice/session-9.scope >> and more >> >> And there are pids in many of the tasks entries under this directories. >> >> And for the blkio: >> /sys/fs/cgroup/blkio/system.slice/ >> /sys/fs/cgroup/blkio/user.slice/ >> /sys/fs/cgroup/blkio/user.slice/user-0.slice/ >> /sys/fs/cgroup/blkio/user.slice/user-0.slice/session-10.scope/ >> /sys/fs/cgroup/blkio/user.slice/user-0.slice/session-2.scope/ >> /sys/fs/cgroup/blkio/user.slice/user-0.slice/session-9.scope/ >> and more. >> >> And here again there are pids in many of the tasks entries under this >> directories. >> >> On the Fedora 20 machine, these entries do not exist, namely there are no >> systemd entries under both /sys/fs/cgroup/memory/ and >> /sys/fs/cgroup/blkio. >> >> Is there a way to disable creating these entries by systemd ? > > Upgrade your systemd version. Old versions will add all controllers to > "delegation" scopes or services. Newer version don't do that. > > Lennart > > -- > Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Avoiding creating systemd memory and blkio controllers under /sys/fs/cgroup/memory and /sys/fs/cgroup/blkio.
Hi everyone, I had a Fedora 20 Machine (x86_64) on which I installed the latest 4.4 kernel released this week (I had built it from source). It had systemd 208. I wanted to test cgroup v2 (not in relation to systemd). In order to be able to activate cgoupv2 memory and cgroup controllers, the cgroup v1 controllers must be disabled. When I unmounted /sys/fs/cgroup/memory and /sys/fs/cgroup/blkio and mounted cgroup v2 on /testv2, cat /testv2/cgroup.controllers showed "memeory" and "io", and everything was fine. Then I installed Fedora 22 on this machine, and it has systemd 219. When I tried this same sequence, of unmounting /sys/fs/cgroup/memory and /sys/fs/cgroup/blkio and mounting cgroup v2 on /testv2, cat /testv2/cgroup.controllers showed nothing. Trying to add disabling cgroup memory controller, by adding cgroup_disable=memory, to the kernel command line caused the system to hang in boot (which is what I expected, but tried anyway...) Trying to solve the problem, I came to the conclusion that this is probably because there are processes in the memory and blkio groups which are held by systemd in F22, and which are not held in F20. On the F22, when I look under /sys/fs/cgouop/memory, I see /sys/fs/cgroup/memory/user.slice/ /sys/fs/cgroup/memory/user.slice/user-0.slice/ /sys/fs/cgroup/memory/user.slice/user-0.slice/session-10.scope /sys/fs/cgroup/memory/user.slice/user-0.slice/session-2.scope /sys/fs/cgroup/memory/user.slice/user-0.slice/session-9.scope and more And there are pids in many of the tasks entries under this directories. And for the blkio: /sys/fs/cgroup/blkio/system.slice/ /sys/fs/cgroup/blkio/user.slice/ /sys/fs/cgroup/blkio/user.slice/user-0.slice/ /sys/fs/cgroup/blkio/user.slice/user-0.slice/session-10.scope/ /sys/fs/cgroup/blkio/user.slice/user-0.slice/session-2.scope/ /sys/fs/cgroup/blkio/user.slice/user-0.slice/session-9.scope/ and more. And here again there are pids in many of the tasks entries under this directories. On the Fedora 20 machine, these entries do not exist, namely there are no systemd entries under both /sys/fs/cgroup/memory/ and /sys/fs/cgroup/blkio. Is there a way to disable creating these entries by systemd ? Regards, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] hostname and dnsdomainname
Hi, I can set a hostname with hostnamectl set-hostname --static newHostname I have a DNS domain server in my local LAN. so when I restart the machine, it gets this full hostname, which can be displayed by hostname -f newHostname.mydomanName and hostname alone shows newHostname Is there some way (for example, restarting some service) by which I can be assigned the domain name without performing a full reboot ? Regards, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Two git trees
Hello, Why are there two git trees: one in git://anongit.freedesktop.org/systemd/systemd and the second in https://github.com/systemd/systemd.git It seems to me that the first one is the primary one, and there are cases when the second tree is not yet synchronized with the first one (which might be confusing) Regards, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Four special object test files
Hi, I noticed this fact: For the following source modules: src/test/test-sched-prio.c src/test/test-sched-prio.c src/test/test-unit-file.c src/test/test-unit-name.c There are the following object files: test_sched_prio-test-sched-prio.o test_cgroup_mask-test-cgroup-mask.o test_unit_file-test-unit-file.o test_unit_name-test-unit-name.o All the other source files (under src/test) have a normal behavior, meaning that for src/test/test-unit-name.c we have: src/test/test-unit-name.o What it the reason for this concatenation? regards, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] stopping a systemd-nspwan container
Hello, I had created a container according to systemd-nspwan man page and ran it by: systemd-nspawn -D/srv/mycontainer I killed it by pkill systemd-nspaw (and not by poweroff from within the container). Now, running machinectl shows that the container still runs: machinectl MACHINE CONTAINER SERVICE mycontainer container nspawn 1 machines listed. but the following is strange: Running: systemd-nspawn -D/srv/mycontainer gives: Spawning namespace container on /srv/mycontainer (console is /dev/pts/2). Init process in the container running as PID 2305. Failed to register machine: File exists Container failed with error code 239. (and running it again gives the same result but with a different pid number). Is there a way to shut down the container which is running in such a scenario ? regards, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] stopping a systemd-nspwan container
Hi, I tried again and now it did work. maybe I was wrong somewhere, sorry. KW On Sat, Mar 22, 2014 at 10:40 PM, Kashyap Chamarthy kcham...@redhat.comwrote: On Sat, Mar 22, 2014 at 04:35:19PM +0200, Kevin Wilson wrote: Hello, I had created a container according to systemd-nspwan man page and ran it by: systemd-nspawn -D/srv/mycontainer I killed it by pkill systemd-nspaw (and not by poweroff from within the container). Now, running machinectl shows that the container still runs: machinectl MACHINE CONTAINER SERVICE mycontainer container nspawn 1 machines listed. but the following is strange: Running: systemd-nspawn -D/srv/mycontainer gives: Spawning namespace container on /srv/mycontainer (console is /dev/pts/2). Init process in the container running as PID 2305. Failed to register machine: File exists Container failed with error code 239. (and running it again gives the same result but with a different pid number). Is there a way to shut down the container which is running in such a scenario ? Hmm, I'm able to shut it down gracefully. I frequently do package builds in systemd-nspawn. Reading your email, I did this below test: On one terminal: $ systemd-nspawn -D /srv/testcontainer Spawning container testcontainer on /srv/testcontainer. Press ^] three times within 1s to abort execution. On another terminal, invoke machinectl: $ machinectl MACHINE CONTAINER SERVICE testcontainercontainer nspawn 1 machines listed. Kill the systemd-nspawn process: $ pkill systemd-nspawn At this point, on the other terminal you see KILL signal invokcation: [. . .] -bash-4.2# Container testcontainer terminated by signal KILL. $ Invoke machinectl again: $ machinectl MACHINE CONTAINER SERVICE 0 machines listed. $ machinectl status testcontainer Could not get path to machine: No machine 'testcontainer' known $ Versions: $ uname -r; rpm -q systemd 3.13.4-200.fc20.x86_64 systemd-210-7.fc21.x86_64 -- /kashyap ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Building systemd from git
Thanks, Zbyszek. --prefix etc. I assume you mean: --prefix /etc and not prefix /etc is it so ? KW On Wed, Mar 19, 2014 at 10:44 PM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Wed, Mar 19, 2014 at 10:25:30PM +0200, Kevin Wilson wrote: Hello, When I build systemd from git using the usual procedure of configure, without setting special parameters, it installs folder under /usr/etc/systemd/ (like /usr/etc/systemd/system and its children, /usr/etc/systemd/network/, and more). That's the usual GNU style. Is there a way to run configure so that, instead of /usr/etc/systemd/, it will use /etc/systemd/ ? In Fedora, for example, the rpm uses the /etc/systemd and not /usr/etc/systemd/, which does not exist. Use --prefix etc. Look ./autogen.sh for some nice default options. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Building systemd from git
Hi all, Thanks for the quick response from all responders; I was afraid that etc here was indeed in a different context than a path regards, KW On Thu, Mar 20, 2014 at 4:08 PM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Thu, Mar 20, 2014 at 04:02:37PM +0200, Kevin Wilson wrote: Thanks, Zbyszek. --prefix etc. I assume you mean: --prefix /etc and not prefix /etc is it so ? No, I meant --prefix as in the command line option to ./configure, e.g. --prefix=/usr, and etc as in et cetera, not the directory. Something like ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var. Generally, it is best to use the same flags that you distribution uses. Then you'll overwrite existing files instead writing them to a different directory and potentially causing confusion. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Building systemd from git
Hello, When I build systemd from git using the usual procedure of configure, without setting special parameters, it installs folder under /usr/etc/systemd/ (like /usr/etc/systemd/system and its children, /usr/etc/systemd/network/, and more). Is there a way to run configure so that, instead of /usr/etc/systemd/, it will use /etc/systemd/ ? In Fedora, for example, the rpm uses the /etc/systemd and not /usr/etc/systemd/, which does not exist. Regards, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] question about name=systemd mount option
Hello, systemd developers, I have a short question about name=systemd cgroup mount option. Would systemd work without specifying this mount option ? what is the reason for using this cgroup mount option ? regards, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd release agent
Hello,
Thanks a lot for your answer and micahl schmidt.
I made several more tests and I wonder whether there are at all
any such tasks with which systemd uses the release agents.
Most of the services uses one process (this is at least what I see when
running cat task from most systemd service folders).
So I assume probably most of them indeed send SIGCHLD to systemd
which is their parent process. (unless someone will pop up and say
that are there any known exceptions to this; I would like to hear
about such exceptions)
There are some exceptions.
Specifically I tried with rsyslog.services and polkit.service.
These two services has each several services in tasks.
with rsyslog.service:
[root@h rsyslog.service]# pstree -p 530
rsyslogd(530)─┬─{rsyslogd}(582)
├─{rsyslogd}(583)
└─{rsyslogd}(584)
ann kill -9 584
gives:
Apr 17 17:59:11 localhost rsyslogd: [origin software=rsyslogd
swVersion=7.2.5 x-pid=8065 x-info=http://www.rsyslog.com;] start
Apr 17 17:59:11 localhost systemd[1]: rsyslog.service: main process
exited, code=killed, status=9/KILL
Apr 17 17:59:11 localhost systemd[1]: Unit rsyslog.service entered failed state
Apr 17 17:59:11 localhost systemd[1]: Starting System Logging Service...
Apr 17 17:59:11 localhost systemd[1]: Started System Logging Service.
The same for polkit:
pstree -p 600
polkitd(600)─┬─{polkitd}(608)
├─{polkitd}(611)
├─{polkitd}(614)
└─{polkitd}(615)
but kill -9 698 did trigger a KILL signal in /var/log/messages:
(and from the ps command we can see that 608 was created by 600).
this is what I see in kernel log:
...
Apr 17 18:02:48 localhost systemd[1]: polkit.service: main process
exited, code=killed, status=9/KILL
Apr 17 18:02:48 localhost systemd[1]: Unit polkit.service entered failed state
...
and of course that systemd-cgroups-agent is missing:
ls /usr/lib/systemd/systemd-cgroups-agent
ls: cannot access /usr/lib/systemd/systemd-cgroups-agent: No such file
or directory
It could be that this threads do send SIGCHLD to systemd. (probably
this is the case).
I wonder if someone knows about a service when a SIGCHLD is not sent?
Or maybe the releas agent is only good for the case when the cgroup
runs empty, when all the grandchildren are dead (as the case
Lennart mentioned).
rgs
Kevin
On Wed, Apr 17, 2013 at 5:48 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 16.04.13 20:45, Kevin Wilson (wkev...@gmail.com) wrote:
cat /sys/fs/cgroup/systemd/system/bluetooth.service/tasks
671
Apr 16 20:40:05 localhost systemd[1]: bluetooth.service: main process
exited, code=killed, status=9/KILL
Apr 16 20:40:05 localhost systemd[1]: Unit bluetooth.service entered
failed state
And with mcelog it was the same:
...
Apr 16 20:33:46 localhost systemd[1]: mcelog.service: main process
exited, code=killed, status=9/KILL
Apr 16 20:33:46 localhost systemd[1]: Unit mcelog.service entered failed
state
...
both folders, bluetooth.service and mcelog.service (under
/sys/fs/cgroup/systemd/system/) were removed.
How come ? could it be that the messages to the DBus are not sent
by systemd-cgroups-agent?
systemd gets both SIGCHLD for its children and cgroup events for the
cgroups they are running in. What you are seening above is the SIGCHLD
working.
SIGCHLD we only get for the processes we ourselves started, but usually
not for processes started by them. SIGCHLD contains exit status
information, such as return code, or signal information.
The cgroup events we get when the cgroup runs empty, when all our
grandchildren are dead, too. It doesn't contain any exist status
information, so is not as nice.
Lennart
--
Lennart Poettering - Red Hat, Inc.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd release agent
Hello, Thanks a lot for your answer. Something is not clear to me with this test I made (on Fedora 18). I hope that someone can explain. I ran: cat /sys/fs/cgroup/systemd/release_agent /usr/lib/systemd/systemd-cgroups-agent No I moved /usr/lib/systemd/systemd-cgroups-agent to some backup. and made sure that: ls /usr/lib/systemd/systemd-cgroups-agent ls: cannot access /usr/lib/systemd/systemd-cgroups-agent: No such file or directory Now I tried killing two services that I know are under systemd cgroups: cat /sys/fs/cgroup/systemd/system/bluetooth.service/tasks 671 Apr 16 20:40:05 localhost systemd[1]: bluetooth.service: main process exited, code=killed, status=9/KILL Apr 16 20:40:05 localhost systemd[1]: Unit bluetooth.service entered failed state And with mcelog it was the same: ... Apr 16 20:33:46 localhost systemd[1]: mcelog.service: main process exited, code=killed, status=9/KILL Apr 16 20:33:46 localhost systemd[1]: Unit mcelog.service entered failed state ... both folders, bluetooth.service and mcelog.service (under /sys/fs/cgroup/systemd/system/) were removed. How come ? could it be that the messages to the DBus are not sent by systemd-cgroups-agent? I also made sure, and ps aux | g systemd-cgroups-agent returns nothing. Any ideas? rgs Kevin On Tue, Apr 9, 2013 at 6:07 PM, Lennart Poettering lenn...@poettering.net wrote: On Tue, 09.04.13 16:39, Kevin Wilson (wkev...@gmail.com) wrote: Hello, On Fedora 18, running: mount | grep release gives: cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) I know and have tried cgroup release_agent; I also noticed that notify_on_release is enabled in systemd cgroups: cat /sys/fs/cgroup/systemd/notify_on_release gives 1 (also in the children, user and system cgroups) what does /usr/lib/systemd/systemd-cgroups-agent do ? what it is for ? What does it do when it is invoked ? it's how the kernel notifies about cgroups running empty. The kernel forks the specified binary out. We install a binary there that simply sends a message on the bus about the cgroup running empty. It's an awful kernel API, but the only one there is for this. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Systemd and cgroups
Thanks! KV On Thu, Apr 11, 2013 at 5:37 PM, Kay Sievers k...@vrfy.org wrote: On Thu, Apr 11, 2013 at 12:46 PM, Kevin Wilson wkev...@gmail.com wrote: Hello, This is a default fedore 18 machine with default kernel. Kernel came with the F18 disto, no changes. No special things like LXC/OpenVZ. So I guess no 3rd party mount any cgroup. then systemd itself will mount all the resource controllers that are compiled into the kernel. How ? I don't know of an API to query from userspace which cgroups are built in into the kernel. Is there such an API ?! /proc/cgroups I will appreciate if someone will point where in systemd code this mounting of all built in kernel cgroups controllers is done. I suppose that systemd mount all controllers **without** name=systemd, am I right ? because the name=systemd does not appear in any controller except /sys/fs/cgroup/systemd (see the initial post in this thread). Is there a way to know whether a mount was done by systemd or not ? All that are found are mounted by PID1. Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Systemd and cgroups
Hello, I have a question about systemd and cgroups: mount | grep cgroups shows that only one entry has name=systemd. and is mounted on /sys/fs/cgroup/systemd . (see below the full output of mount | grep cgroups Is it true that all other cgroup entry shown by mount | grep cgroups were not mounted by systemd (and may be unmounted without directly causing problems is systemd)? tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) rgs Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd release agent
Hello, On Fedora 18, running: mount | grep release gives: cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) I know and have tried cgroup release_agent; I also noticed that notify_on_release is enabled in systemd cgroups: cat /sys/fs/cgroup/systemd/notify_on_release gives 1 (also in the children, user and system cgroups) what does /usr/lib/systemd/systemd-cgroups-agent do ? what it is for ? What does it do when it is invoked ? regars, Kevin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
