On 12/14/2013 12:20 AM, Lennart Poettering wrote:
On Fri, 13.12.13 16:15, Lennart Poettering (lenn...@poettering.net) wrote:
We had discussed this back at Linux Plumbers last year, and at the time
you had suggested that rather than create /dev/ttyN symlinks we should
instead do something
Hi,
As we know, systemd only forks getty on ttyX when we press ctrl + alt + FX.
I whould like to let systemd forks server gettys on all of tty deivces by
default.
this is very useful in container environment, since we can't use ctrl+alt+FX
to trigger getty in container.
If there are some
Hello Mantas,
On 12/13/2013 04:17 PM, Mantas Mikulėnas wrote:
On Dec 13, 2013 10:09 AM, Gao feng gaof...@cn.fujitsu.com
mailto:gaof...@cn.fujitsu.com wrote:
Hi,
As we know, systemd only forks getty on ttyX when we press ctrl + alt + FX.
I whould like to let systemd forks server gettys
On 09/25/2013 08:23 AM, Lennart Poettering wrote:
On Tue, 24.09.13 08:36, Gao feng (gaof...@cn.fujitsu.com) wrote:
Some programs need to set the memory.use_hierarchy(such as libvirt),
Add this feature.
As mentioned already: this really shouldn't be configurable but simply
the unconditional
Show MemoryHierarchy in cgroup_context_dump.
---
src/core/cgroup.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/cgroup.c b/src/core/cgroup.c
index 68615c3..362b074 100644
--- a/src/core/cgroup.c
+++ b/src/core/cgroup.c
@@ -92,6 +92,7 @@ void cgroup_context_dump(CGroupContext *c,
Some programs need to set the memory.use_hierarchy(such as libvirt),
Add this feature.
---
src/core/cgroup.c | 6 ++
src/core/cgroup.h | 1 +
src/core/dbus-cgroup.c| 16
src/core/load-fragment-gperf.gperf.m4 | 1 +
4
support setting MemoryHierarchy of unit through systemctl.
---
src/systemctl/systemctl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index 8b9183d..7d251a0 100644
--- a/src/systemctl/systemctl.c
+++ b/src/systemctl/systemctl.c
@@
---
man/systemd.cgroup.xml | 11 +++
1 file changed, 11 insertions(+)
diff --git a/man/systemd.cgroup.xml b/man/systemd.cgroup.xml
index ac58962..f347f1b 100644
--- a/man/systemd.cgroup.xml
+++ b/man/systemd.cgroup.xml
@@ -135,6 +135,17 @@ along with systemd; If not, see
On 09/24/2013 05:06 AM, Lennart Poettering wrote:
On Mon, 23.09.13 14:30, Gao feng (gaof...@cn.fujitsu.com) wrote:
Some programs need to set the memory.use_hierarchy(such as libvirt),
Add this feature.
As mentioned already: this really shouldn't be configurable but simply
On 09/18/2013 12:56 AM, Lennart Poettering wrote:
On Tue, 17.09.13 17:45, Lennart Poettering (lenn...@poettering.net) wrote:
1, set up when systemd creates cpuset cgroup for machine.slice?
2, the programs which create the machines?
3, other ideas? kernel?
I have the suspicion that we need
On 09/13/2013 08:26 PM, Lennart Poettering wrote:
On Fri, 13.09.13 17:49, Gao feng (gaof...@cn.fujitsu.com) wrote:
Some programs need to set the memory.use_hierarchy(such as libvirt),
Add this feature.
Hmm, should this really be an option? Shouldn't we much rather turn
---
src/core/cgroup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/core/cgroup.c b/src/core/cgroup.c
index 1f41efc..9277dd6 100644
--- a/src/core/cgroup.c
+++ b/src/core/cgroup.c
@@ -92,7 +92,7 @@ void cgroup_context_dump(CGroupContext *c, FILE* f, const
char *prefix)
Hi
I'm working on adding set cpuset cgroup support for systemd.
this work almost finished. but I faced a problem.
As we know, if we create a machine,the cgroup for this machine
will be created as well. and the cgroup of this machine is a
sub-directory of machine.slice(or other slices..). And if
If the memory_limit of unit is -1, we should write -1
to the file memory.limit_in_bytes. not the (unit64_t) -1.
otherwise the memory.limit_in_bytes will be set to zero.
---
src/core/cgroup.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/src/core/cgroup.c
Some programs need to set the memory.use_hierarchy(such as libvirt),
Add this feature.
---
src/core/cgroup.c | 9 +
src/core/cgroup.h | 1 +
src/core/dbus-cgroup.c| 16
src/core/load-fragment-gperf.gperf.m4 | 1 +
Show MemoryHierarchy in cgroup_context_dump.
---
src/core/cgroup.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/cgroup.c b/src/core/cgroup.c
index 336d394..2c8aa22 100644
--- a/src/core/cgroup.c
+++ b/src/core/cgroup.c
@@ -91,6 +91,7 @@ void cgroup_context_dump(CGroupContext *c,
support setting MemoryHierarchy of unit through systemctl.
---
src/systemctl/systemctl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index 57e5bb9..87388bb 100644
--- a/src/systemctl/systemctl.c
+++ b/src/systemctl/systemctl.c
@@
We can simply limit the total memory usage of machines
through setting the memory usage limit of machine.slice.
---
units/machine.slice | 3 +++
1 file changed, 3 insertions(+)
diff --git a/units/machine.slice b/units/machine.slice
index 3d40dfd..c959598 100644
--- a/units/machine.slice
+++
add the manpage for MemoryHierarchy.
---
man/systemd.cgroup.xml | 11 +++
1 file changed, 11 insertions(+)
diff --git a/man/systemd.cgroup.xml b/man/systemd.cgroup.xml
index cc0eb15..80fc2e2 100644
--- a/man/systemd.cgroup.xml
+++ b/man/systemd.cgroup.xml
@@ -135,6 +135,17 @@ along with
set the value of variable r to the return value
of cg_set_attribute.
---
src/core/cgroup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/core/cgroup.c b/src/core/cgroup.c
index 3eeb475..fba0b2f 100644
--- a/src/core/cgroup.c
+++ b/src/core/cgroup.c
@@ -264,7 +264,7 @@
it should be memory.soft_limit_in_bytes.
---
src/core/cgroup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/core/cgroup.c b/src/core/cgroup.c
index fba0b2f..aee93ba 100644
--- a/src/core/cgroup.c
+++ b/src/core/cgroup.c
@@ -266,7 +266,7 @@ void
On 09/11/2013 08:07 PM, Lennart Poettering wrote:
On Wed, 11.09.13 09:18, Gao feng (gaof...@cn.fujitsu.com) wrote:
The SYSTEMD.CGROUP(5) said if MemoryLimit=bytes is set for unit, it
implies MemeoryAccounting=true for this unit.
But seems systemd didn't implement this hint. CPUShares
On 09/10/2013 11:50 PM, Lennart Poettering wrote:
On Mon, 26.08.13 11:19, Gao feng (gaof...@cn.fujitsu.com) wrote:
Hi
The SYSTEMD.CGROUP(5) said if MemoryLimit=bytes is set for unit, it
implies MemeoryAccounting=true for this unit.
But seems systemd didn't implement this hint. CPUShares
On 09/10/2013 11:13 PM, Lennart Poettering wrote:
On Fri, 30.08.13 10:56, Gao feng (gaof...@cn.fujitsu.com) wrote:
if we get BlockIOReadBandwidth=, we should only remove the
read-bandwidth-entries in blockio_device_bandwidths list.
Thanks! Applied, though with one change:
+read
if we get BlockIOReadBandwidth=, we should only remove the
read-bandwidth-entries in blockio_device_bandwidths list.
---
src/core/load-fragment.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/src/core/load-fragment.c b/src/core/load-fragment.c
index
This patch adds the support for setting up BlockIORead/WriteBandwidth
in bus_cgroup_set_property.
---
src/core/dbus-cgroup.c | 101 +
1 file changed, 101 insertions(+)
diff --git a/src/core/dbus-cgroup.c b/src/core/dbus-cgroup.c
index
This patch allows user to set up BlockIOReadBandwidth and BlockIOWriteBandwidth
for unit through systemctl. Such as
systemctl set-property sshd.service BlockIOReadBandwidth=/dev/sda 10
systemctl set-property sshd.service BlockIOWriteBandwidth=/dev/sda 20
---
src/systemctl/systemctl.c |
On 08/28/2013 07:45 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Aug 26, 2013 at 11:19:54AM +0800, Gao feng wrote:
Hi
The SYSTEMD.CGROUP(5) said if MemoryLimit=bytes is set for unit, it
implies MemeoryAccounting=true for this unit.
But seems systemd didn't implement this hint. CPUShares
BlockIOReadBandwidth and BlockIOWriteBandwidth both use
config_parse_blockio_bandwidth to set up CGroupBlockIODeviceBandwidth,
We should set the read value based on the left values
in config files.
---
src/core/load-fragment.c | 1 +
1 file changed, 1 insertion(+)
diff --git
If a device node is already in the device_allow list of
CGroupContext, we should replace it instead of create a
new one and append this new one to the end of device_allow
list.
---
src/core/dbus-cgroup.c | 32 +++-
1 file changed, 23 insertions(+), 9 deletions(-)
diff
This patch adds the support for setting up BlockIODeviceWeight
in bus_cgroup_set_property. most of the codes are copied from
the case that sets up DeviceAllow.
---
src/core/dbus-cgroup.c | 85 ++
1 file changed, 85 insertions(+)
diff --git
This patch allows user to set up BlockIODeviceWeight for unit
through systemctl. Such as
systemctl set-property sshd.service BlockIODeviceWeight=/dev/sda 100
---
src/systemctl/systemctl.c | 37 +
1 file changed, 37 insertions(+)
diff --git
We can use systemctl show unitname to show the BlockIODeviceWeight
of unit.
---
src/systemctl/systemctl.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index ff29b0f..4ea301a 100644
--- a/src/systemctl/systemctl.c
+++
On 08/26/2013 02:16 AM, James Bottomley wrote:
On Sun, 2013-08-25 at 19:37 +0200, Kay Sievers wrote:
On Sun, Aug 25, 2013 at 7:16 PM, James Bottomley
jbottom...@parallels.com wrote:
On Wed, 2013-08-21 at 11:51 +0200, Kay Sievers wrote:
On Wed, Aug 21, 2013 at 9:22 AM, Gao feng gaof
If the mode is UNIT_CHECK,it means we only want to check if
the paramaters are valid. the first round of cycle already
did this check, no need to check again.
---
src/core/dbus-unit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/core/dbus-unit.c b/src/core/dbus-unit.c
On 08/26/2013 11:19 AM, James Bottomley wrote:
On Mon, 2013-08-26 at 09:06 +0800, Gao feng wrote:
On 08/26/2013 02:16 AM, James Bottomley wrote:
On Sun, 2013-08-25 at 19:37 +0200, Kay Sievers wrote:
On Sun, Aug 25, 2013 at 7:16 PM, James Bottomley
jbottom...@parallels.com wrote:
On Wed, 2013
We should set up blockio_weight not cpu_shares.
Signed-off-by: Gao feng gaof...@cn.fujitsu.com
---
src/core/dbus-cgroup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/core/dbus-cgroup.c b/src/core/dbus-cgroup.c
index 8ad3d11..9e97b20 100644
--- a/src/core/dbus-cgroup.c
cc libvirt-list
On 08/21/2013 01:30 PM, Eric W. Biederman wrote:
Gao feng gaof...@cn.fujitsu.com writes:
Unix sockets are private resources of net namespace,
allowing one net namespace to access to other netns's unix
sockets is meaningless.
Allowing one net namespace to access another
On 08/21/2013 03:06 PM, Eric W. Biederman wrote:
Gao feng gaof...@cn.fujitsu.com writes:
cc libvirt-list
On 08/21/2013 01:30 PM, Eric W. Biederman wrote:
Gao feng gaof...@cn.fujitsu.com writes:
Unix sockets are private resources of net namespace,
allowing one net namespace to access
in container, the
shutdown message will be send to the systemd-shutdownd
through unix socket /run/systemd/private, and because
systemd-shutdownd is running in host, so finally, the host
will become shutdown.
We should make sure unix sockets are per net namespace to
avoid this problem.
Signed-off-by: Gao
cc contain...@lists.linux-foundation.org
On 08/21/2013 12:31 PM, Gao feng wrote:
Unix sockets are private resources of net namespace,
allowing one net namespace to access to other netns's unix
sockets is meaningless.
I'm researching a problem about shutdown from container,
if the cotainer
41 matches
Mail list logo
