FYI

----- Forwarded message from Juliusz Chroboczek 
<j...@pps.univ-paris-diderot.fr> -----

Date: Mon, 08 Sep 2014 16:03:56 +0200
From: Juliusz Chroboczek <j...@pps.univ-paris-diderot.fr>
To: Baptiste Jonglez <bjong...@illyse.org>
Cc: openwrt-devel@lists.openwrt.org, babel-us...@lists.alioth.debian.org
Subject: Re: [Babel-users] [OpenWrt-Devel] [PATCH] babeld: use procd to start,
        stop, and respawn
User-Agent: Wanderlust/2.15.9

>> adds a hotplug.d file to restart babeld when interfaces go up or down.

> https://github.com/openwrt-routing/packages/pull/52

> However [...] this should not be needed, as babeld detects
> when an interface is brought up and then starts using it.

Yes, note however that babeld only watches the interfaces that were given
to it on the command line or in the config file.  Does OpenWRT need
wildcard support?

>> Additionally adds a patch to the babeld source is to prevent the
>> attempted recreation of a pidfile when babeld restarts uncleanly.

Please don't do that.  We're trying to avoid having the OpenWRT version of
babeld diverge from upstream, as a patched babeld is confusing to both the
users and the maintainers.

>> This is also possible to do by passing -I '' on the command line,
>> however procd interprets an empty argument terminating the list, and
>> thus cannot supply empty arguments to programs it manages.

If this cannot be fixed without hacking babeld, I can add a special case
so that "-I none" is a synonim for "-I ''".

-- Juliusz



----- End forwarded message -----

Attachment: pgpoR4xiD3th_.pgp
Description: PGP signature

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to