[systemd-devel] [question] networkd: Any support for hooks?

Cameron Norman camerontnorman at gmail.com
Thu Oct 2 19:48:16 PDT 2014


On Wed, Oct 1, 2014 at 10:36 PM, Tom Gundersen <teg at jklm.no> wrote:
> Hi Cameron,
>
> On Thu, Oct 2, 2014 at 6:36 AM, Cameron Norman <camerontnorman at gmail.com> wrote:
>> ifupdown [1], NetworkManager, and WICD all support hooks for when a
>> network interface is configured or deconfigured (before and after
>> these actions).
>>
>> Are there any plans to support something along these lines? If so,
>> what will that look like?
>>
>> If there are no plans, how do networkd's developers feel about adding
>> the feature (will not merge, or will accept patches, etc.) ?
>
> I am sceptical to adding hooks, so would need a lot of convincing.
> What we do, however, is to expose the configuration state using the
> sd-network C API, which external programs can watch and react on (see
> how timesyncd and resolved currently works).

Does the C API allow programs to temporarily stall bringing up or down
the interface, or does it only deliver signals of if state?

Out of curiosity, where does your aversion to hooks come from? Does it
add significant complication code wise, or is it more with respect to
using networkd before any filesystems are mounted (thus the hook files
would not be present)?

Cheers,
--
Cameron


More information about the systemd-devel mailing list