From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 1/2] net: linkwatch: send change uevent on link changes Date: Tue, 04 Dec 2018 20:49:59 -0800 (PST) Message-ID: <20181204.204959.1231535397902751562.davem@davemloft.net> References: <20181201160021.GA4948@Mindship-05.localdomain> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: j.witteveen@gmail.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:54588 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725865AbeLEEuA (ORCPT ); Tue, 4 Dec 2018 23:50:00 -0500 In-Reply-To: <20181201160021.GA4948@Mindship-05.localdomain> Sender: netdev-owner@vger.kernel.org List-ID: From: Jouke Witteveen Date: Sat, 1 Dec 2018 17:00:21 +0100 > Make it easy for userspace to respond to acquisition/loss of carrier. > The uevent is picked up by udev and, on systems with systemd, the > device unit of the interface announces a configuration reload. > > Signed-off-by: Jouke Witteveen > --- > I did not want to change the commit message into a systemd-howto, but > subscribing to udev events can be done through a line like > ReloadPropagatedFrom=sys-subsystem-net-devices-%i.device > in a systemd unit file. I want to hear more about "why". If we have the rtnetlink message that can be listened for, userspace ought to use that. That's what it is there for.