Re: [systemd-devel] systemd-networkd bridge with DHCP working

2014-03-22 Thread Tom Gundersen
On Sat, Mar 22, 2014 at 5:06 AM, poma pomidorabelis...@gmail.com wrote: systemd-networkd bridge dhcp OK https://bugzilla.redhat.com/attachment.cgi?id=877526 Thanks for reporting back. Cheers, Tom ___ systemd-devel mailing list

Re: [systemd-devel] A potentially cross platform solution forprocess containment in init applications

2014-03-22 Thread Benjamin SANS
* On Friday, 21 March 2014 19:42, Greg KH gre...@linuxfoundation.org wrote: Great, I suggest you try it out and see how it works. Patches are always gladly accepted. I'm not so sure of that, but if you say so... -- Benjamin SANS ___ systemd-devel

[systemd-devel] stopping a systemd-nspwan container

2014-03-22 Thread Kevin Wilson
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

Re: [systemd-devel] [PATCH 2/2] domain: grab the domain's parent lock only when needed

2014-03-22 Thread Daniel Mack
On 03/21/2014 12:35 PM, Djalal Harouni wrote: I've two questions: 1) Can we improve it in ordre to reduce the lock hold time ? We don't consider that a very frequent operation, so we never thought about optimizing this code path. What use case do you have in mind so that performance would

[systemd-devel] [PATCH 1/1] sd-rtnl: Introduce container parsing

2014-03-22 Thread Susant Sahani
Introducing generic container parsing . Now supported for type FLA_INFO_KIND and IFLA_VLAN_ID which can be extended to other container parsing which is based on table based look up. --- src/libsystemd/sd-rtnl/rtnl-internal.h | 20 + src/libsystemd/sd-rtnl/rtnl-message.c | 79

Re: [systemd-devel] [PATCH] README: Correct EFI requirements

2014-03-22 Thread Kay Sievers
On Sat, Mar 22, 2014 at 1:41 AM, Thomas Bächler tho...@archlinux.org wrote: systemd does not need or use CONFIG_EFI_VARS anywhere, this should be CONFIG_EFIVAR_FS instead. --- README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Applied. Thanks, Kay

Re: [systemd-devel] [PATCH 2/2] domain: grab the domain's parent lock only when needed

2014-03-22 Thread Kay Sievers
On Fri, Mar 21, 2014 at 12:35 PM, Djalal Harouni tix...@opendz.org wrote: On Thu, Mar 20, 2014 at 10:58:21AM +0100, Daniel Mack wrote: /* link into parent domain */ if (parent) { What if 'parent' was already unrefed at this point? That can happen any time as soon we give up the

Re: [systemd-devel] [PATCH 2/2] domain: grab the domain's parent lock only when needed

2014-03-22 Thread Kay Sievers
On Sat, Mar 22, 2014 at 3:43 PM, Daniel Mack dan...@zonque.org wrote: On 03/21/2014 12:35 PM, Djalal Harouni wrote: I've two questions: 1) Can we improve it in ordre to reduce the lock hold time ? We don't consider that a very frequent operation, so we never thought about optimizing this

Re: [systemd-devel] [PATCH 2/2] domain: grab the domain's parent lock only when needed

2014-03-22 Thread Djalal Harouni
On Sat, Mar 22, 2014 at 07:37:38PM +0100, Kay Sievers wrote: On Sat, Mar 22, 2014 at 3:43 PM, Daniel Mack dan...@zonque.org wrote: Also it seems that now there is only support for one level of nested domains? will this be increased? I don't think so. What's your use case here? We never

Re: [systemd-devel] [PATCH 2/2] domain: grab the domain's parent lock only when needed

2014-03-22 Thread Kay Sievers
On Sat, Mar 22, 2014 at 7:56 PM, Djalal Harouni tix...@opendz.org wrote: On Sat, Mar 22, 2014 at 07:37:38PM +0100, Kay Sievers wrote: On Sat, Mar 22, 2014 at 3:43 PM, Daniel Mack dan...@zonque.org wrote: Also it seems that now there is only support for one level of nested domains? will this

Re: [systemd-devel] [PATCH 2/2] domain: grab the domain's parent lock only when needed

2014-03-22 Thread Djalal Harouni
On Sat, Mar 22, 2014 at 08:28:38PM +0100, Kay Sievers wrote: On Sat, Mar 22, 2014 at 7:56 PM, Djalal Harouni tix...@opendz.org wrote: On Sat, Mar 22, 2014 at 07:37:38PM +0100, Kay Sievers wrote: On Sat, Mar 22, 2014 at 3:43 PM, Daniel Mack dan...@zonque.org wrote: Also it seems that now

Re: [systemd-devel] stopping a systemd-nspwan container

2014-03-22 Thread Kashyap Chamarthy
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

Re: [systemd-devel] stopping a systemd-nspwan container

2014-03-22 Thread Kevin Wilson
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