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.
On Wed, 13.02.13 08:49, Thomas Graf ([email protected]) 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
On Wed, Feb 13, 2013 at 12:10 PM, Colin Guthrie 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 the core systemd.
Lo
'Twas brillig, and Lennart Poettering at 13/02/13 03:06 did gyre and gimble:
> On Tue, 12.02.13 14:07, Thomas Graf ([email protected]) 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
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 contradictin
On Wed, 06.02.13 16:27, Ian Pilcher ([email protected]) wrote:
> * Removing network.target from the Before=... line in
> openvswitch.service is not an option. See comment #1 of that bug.
So, you need to figure out what you want here... You cannot have a
service A both start after B and star
On Tue, 12.02.13 14:07, Thomas Graf ([email protected]) 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 the bug,
> >>there is a SYSTEMCTL_IGNORE_DEPENDENCIES=1 env var you can
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 --ignore-dependen
'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 openvswitc
On 02/07/2013 10:09 AM, Frederic Crozat wrote:
> We have exactly the same issue on openSUSE with some network services,
> and we are using --ignore-dependencies in those case (because --no-block
> is not always the "right" solution).
Yeah. I thrashed around for a couple of days until I finally yo
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 --ignore-dependencies
> argument if it redirects to syste
Le jeudi 07 février 2013 à 09:55 -0600, Ian Pilcher a écrit :
> On 02/07/2013 06:13 AM, Colin Guthrie wrote:
> > 'Twas brillig, and Ian Pilcher at 06/02/13 22:27 did gyre and gimble:
> >> * systemd sees "Before=... network.target" in openvswitch.service and
> >> waits for the network service to c
On 02/07/2013 06:13 AM, Colin Guthrie wrote:
> 'Twas brillig, and Ian Pilcher at 06/02/13 22:27 did gyre and gimble:
>> * systemd sees "Before=... network.target" in openvswitch.service and
>> waits for the network service to complete -- which will never happen,
>> because the network service i
'Twas brillig, and Ian Pilcher at 06/02/13 22:27 did gyre and gimble:
> Recently, Fedora shipped an update which starts the Open vSwitch service
> on demand -- whenever an Open vSwitch bridge or port is "ifup'ed". In
> theory, I should now be able to simply write traditional ifcfg-* files
> for al
Recently, Fedora shipped an update which starts the Open vSwitch service
on demand -- whenever an Open vSwitch bridge or port is "ifup'ed". In
theory, I should now be able to simply write traditional ifcfg-* files
for all of my interfaces and use the "network" service to start them.
Unfortunately
15 matches
Mail list logo
