Thanks Ian
I tried to change Before = network.target to After = network.target but
same issue..
what do you think it would bring to add this oneshot service as I see it
only launch the openvswitch-nonetwork.service?
On 01/08/16 16:51, Ian Pilcher wrote:
On 01/08/2016 09:27 AM, Benoît wrote:
it is using /etc/systemd/network
and to start ovs :
/etc/systemd/system/multi-user.target.wants/ovs-vswitchd.service
[Unit]
Description = Open vSwitch Daemon
Documentation = man:ovs-vswitchd
Wants = network.target
Before = network.target
Requires = ovsdb-server.service
After = ovsdb-server.service
[Service]
ExecStartPre = /sbin/modprobe openvswitch
PIDFile = /run/openvswitch/ovs-vswitchd.pid
ExecStart = /usr/sbin/ovs-vswitchd
--pidfile=/run/openvswitch/ovs-vswitchd.pid
It looks like Arch hasn't split the Open vSwitch service into pre- and
post-network stages. Here's what Fedora does:
$ cat openvswitch.service
[Unit]
Description=Open vSwitch
After=syslog.target network.target openvswitch-nonetwork.service
Requires=openvswitch-nonetwork.service
[Service]
Type=oneshot
ExecStart=/bin/true
ExecStop=/bin/true
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
$ cat openvswitch-nonetwork.service
[Unit]
Description=Open vSwitch Internal Unit
After=syslog.target
PartOf=openvswitch.service
Wants=openvswitch.service
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=-/etc/sysconfig/openvswitch
ExecStart=/usr/share/openvswitch/scripts/ovs-ctl start \
--system-id=random $OPTIONS
ExecStop=/usr/share/openvswitch/scripts/ovs-ctl stop
RuntimeDirectory=openvswitch
RuntimeDirectoryMode=0755
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
