ok, sorry, this message can be ignored, I see github changes on Mar 17 to
reflect the ‘ip link’ change, but I think that the
'/etc/init.d/openvswitch-switch status’ may still be a problem.
> On 24 May 2017, at 08:42, Raymond Burkholder <r...@oneunified.net> wrote:
>
> This probably isn’t an optimal solution, as openvswitch runs on a number of
> different platforms. I am not sure how to perform a proper selection of
> ifconfig vs ip link. But i think I noticed some other openvswitch scripts
> use ip link only.
>
> The first change below relates to my previous message about systemd doing
> weird things with service status.
>
> # diff /usr/share/openvswitch/scripts/ifupdown.sh.old
> /usr/share/openvswitch/scripts/ifupdown.sh
> 27d26
> <
> 32c31
> < if /etc/init.d/openvswitch-switch status > /dev/null 2>&1; then :; else
> ---
>> if /etc/init.d/openvswitch-switch ovsstatus > /dev/null 2>&1; then :; else
> 38d36
> <
> 52,53c50
> <
> < ifconfig "${IFACE}" up
> ---
>> ip link set dev ${IFACE} up
> 60c57
> < ifconfig "${IFACE}" up
> ---
>> ip link set dev ${IFACE} up
> 67c64
> < ifconfig "${IFACE}" up
> ---
>> ip link set dev ${IFACE} up
> 70c67
> < ifconfig "${slave}" up
> ---
>> ip link set dev ${slave} up
>
> And as followup, here is the systemd version:
>
> # systemd --version
> systemd 232
> +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
> +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
>
>
>
> Raymond Burkholder
> https://blog.raymond.burkholder.net
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
