On 07/11/2013 07:58 PM, Richard Weinberger wrote:
Am 11.07.2013 11:49, schrieb Daniel P. Berrange:
> On Thu, Jul 11, 2013 at 11:44:48AM +0200, Richard Weinberger wrote:
>> Am 11.07.2013 11:42, schrieb Gao feng:
>>> On 07/11/2013 03:18 PM, Richard Weinberger wrote:
>>>> This morning I've installed a wrapper around ip to show me the
process tree upon ip link ... down is used.
>>>> The log showed this:
>>>>
>>>> 769 ? Ss 0:00 /usr/lib/systemd/systemd-udevd
>>>> 17759 ? S 0:00 \_ /usr/lib/systemd/systemd-udevd
>>>> 17764 ? S 0:00 \_ /usr/lib/systemd/systemd-udevd
>>>> 17772 ? S 0:00 \_ /usr/lib/systemd/systemd-udevd
>>>> 19477 ? S 0:00 | \_ /bin/bash /sbin/ifdown veth5 -o
hotplug
>>>> 19910 ? S 0:00 | \_ /sbin/ip link set dev veth5 down
>>>>
>>>> Now I have to urge to use a "Kantholz". ;-)
>>>>
>>>
>>> hmmm...
>>>
>>> it's systemd... I have no idea now... :(
>>
>> TBH it is not systemd's fault.
>> OpenSUSE's /usr/lib/udev/rules.d/77-network.rules did not white list veth*
devices.
>> Therefore systemd-udevd called ifup/down and other hotplug magic.
>
> Ah ha, that's a nice issue :-) I assume you've filed a bug against opensuse
> to fix this ? Can you post a link to the bug here for the sake of archive
> records.
Sure:
https://bugzilla.novell.com/show_bug.cgi?id=829033
It's good news we know what causes veth device down. :)