Re: [systemd-devel] network/openvswitch dependency loop/deadlock

2013-02-13 Thread Colin Guthrie
'Twas brillig, and Lennart Poettering at 13/02/13 03:06 did gyre and gimble: On Tue, 12.02.13 14:07, Thomas Graf (tg...@redhat.com) wrote: On 02/07/2013 04:55 PM, Ian Pilcher wrote: On 02/07/2013 06:13 AM, Colin Guthrie wrote: Also re the initscripts tweaks and the if statement proposed in

Re: [systemd-devel] network/openvswitch dependency loop/deadlock

2013-02-13 Thread Kay Sievers
On Wed, Feb 13, 2013 at 12:10 PM, Colin Guthrie gm...@colin.guthr.ie wrote: Either way, is a generator the way to go here longer term, or is there some other plan afoot to modernise the static network configs? The static network config files, file format and parsing will some day be part of

Re: [systemd-devel] network/openvswitch dependency loop/deadlock

2013-02-13 Thread Lennart Poettering
On Wed, 13.02.13 08:49, Thomas Graf (tg...@redhat.com) wrote: On 02/13/2013 04:06 AM, Lennart Poettering wrote: Well, there still is a dep loop, that is unfixed, right? I mean, you want your service to run as part of bringing up some networks, but also after the network is up. So what do

Re: [systemd-devel] network/openvswitch dependency loop/deadlock

2013-02-13 Thread Thomas Graf
On 02/13/2013 08:03 PM, Lennart Poettering wrote: Well, so first of all, no service needs syslog.service anymore. The socket of syslog is established during early boot, and you should not add deps for it anymore. OK, I'll remove that dependency. We inherited that from the upstream unit file.

Re: [systemd-devel] network/openvswitch dependency loop/deadlock

2013-02-12 Thread Thomas Graf
On 02/07/2013 04:55 PM, Ian Pilcher wrote: On 02/07/2013 06:13 AM, Colin Guthrie wrote: Also re the initscripts tweaks and the if statement proposed in the bug, there is a SYSTEMCTL_IGNORE_DEPENDENCIES=1 env var you can export that will make service openvswitch start pass the

Re: [systemd-devel] network/openvswitch dependency loop/deadlock

2013-02-12 Thread Thomas Graf
On 02/13/2013 04:06 AM, Lennart Poettering wrote: Well, there still is a dep loop, that is unfixed, right? I mean, you want your service to run as part of bringing up some networks, but also after the network is up. So what do you want now? Start it after or at the same time, that's

Re: [systemd-devel] network/openvswitch dependency loop/deadlock

2013-02-10 Thread Colin Guthrie
'Twas brillig, and Ian Pilcher at 08/02/13 21:00 did gyre and gimble: On 02/07/2013 06:13 AM, Colin Guthrie wrote: Also re the initscripts tweaks and the if statement proposed in the bug, there is a SYSTEMCTL_IGNORE_DEPENDENCIES=1 env var you can export that will make service openvswitch start