Re: [systemd-devel] Reboot hangs at the very last step

2016-07-20 Thread Frank Steiner
Andrei Borzenkov wrote >> Should the mnt-raid2\x2dbackup.mount contain sth. like >> "After=network.service"? > > Many dependencies are added implicitly and are not present in unit > definition. Please show output of > > systemctl show -p Before -p After mnt-raid2.mount > systemctl show -p

Re: [systemd-devel] Reboot hangs at the very last step

2016-07-20 Thread Colin Guthrie
Andrei Borzenkov wrote on 20/07/16 11:54: > On Wed, Jul 20, 2016 at 12:20 PM, Colin Guthrie wrote: > >> >> Is it enough to just add the "_netdev" option to the fstab mounts in >> question? > > The problem is triggered by manual mounts; here _netdev is irrelevant. Fair

Re: [systemd-devel] Reboot hangs at the very last step

2016-07-20 Thread Andrei Borzenkov
On Wed, Jul 20, 2016 at 12:20 PM, Colin Guthrie wrote: > > Is it enough to just add the "_netdev" option to the fstab mounts in > question? The problem is triggered by manual mounts; here _netdev is irrelevant. ___ systemd-devel

[systemd-devel] Fwd: journalctl - RuntimeMaxUse attribute in journald.conf behavior is not correct

2016-07-20 Thread sandeep
Hi, I was performing some tests related to below attributes in Journald.conf RuntimeMaxUse RuntimeMaxFileSize RuntimeMaxFiles I am not sure whether some of the behavior is correct or not. Please clarify. *1) Test1* RuntimeMaxUse=2G #RuntimeKeepFree= RuntimeMaxFileSize=2G RuntimeMaxFiles=2

Re: [systemd-devel] Confining ALL processes to a CPUs/RAM via cpuset controller

2016-07-20 Thread Daniel P. Berrange
On Wed, Jul 20, 2016 at 03:29:30PM +0200, Lennart Poettering wrote: > On Wed, 20.07.16 12:53, Daniel P. Berrange (berra...@redhat.com) wrote: > > > For virtualized hosts it is quite common to want to confine all host OS > > processes to a subset of CPUs/RAM nodes, leaving the rest available for >

Re: [systemd-devel] Confining ALL processes to a CPUs/RAM via cpuset controller

2016-07-20 Thread Lennart Poettering
On Wed, 20.07.16 14:49, Daniel P. Berrange (berra...@redhat.com) wrote: > > > The key factor here is use of "Before" to ensure this gets run immediately > > > after systemd switches root out of the initrd, and before /any/ long lived > > > services are run. This lets us set cpuset placement on

Re: [systemd-devel] Confining ALL processes to a CPUs/RAM via cpuset controller

2016-07-20 Thread Lennart Poettering
On Wed, 20.07.16 12:53, Daniel P. Berrange (berra...@redhat.com) wrote: > For virtualized hosts it is quite common to want to confine all host OS > processes to a subset of CPUs/RAM nodes, leaving the rest available for > exclusive use by QEMU/KVM. Historically people have used the "isolcpus" >

[systemd-devel] Confining ALL processes to a CPUs/RAM via cpuset controller

2016-07-20 Thread Daniel P. Berrange
For virtualized hosts it is quite common to want to confine all host OS processes to a subset of CPUs/RAM nodes, leaving the rest available for exclusive use by QEMU/KVM. Historically people have used the "isolcpus" kernel arg todo this, but last year that had its semantics changed, so that any