which specific package is causing issue ?
In my setup, I've noticed this with dnsmasq and babeld. That is,
that I needed to restart and instead of reload to get things to
take effect. Everything else I run is configured by command line
arguments.
what do you want to do ? track a
On 15/09/2014 10:36, Tristan Plumb wrote:
which specific package is causing issue ?
In my setup, I've noticed this with dnsmasq and babeld. That is,
that I needed to restart and instead of reload to get things to
take effect. Everything else I run is configured by command line
, Tristan Plumb wrote:
Currently procd enabled initscripts will restart on reload when the command
line changes, which works for many packages, but not anything that keeps its
configuration in a file, like dnsmasq.
Wouldn't it be better to check whether the generated config file changed
On 14/09/2014 17:37, Baptiste Jonglez wrote:
On Sun, Sep 14, 2014 at 08:14:11AM -0400, Tristan Plumb wrote:
Currently procd enabled initscripts will restart on reload when
the command line changes, which works for many packages, but not
anything that keeps its configuration in a file
Baptiste Jonglez wrote:
Note that babeld is maintained in https://github.com/openwrt-routing/packages.
Nevertheless, comments inline.
So I found, after I had sent this off. In future I'll send pull-requests
there.
adds a hotplug.d file to restart babeld when interfaces go up or down.
'' on the command line, however procd
interprets an empty argument terminating the list, and thus cannot supply
empty arguments to programs it manages.
Signed-off-by: Tristan Plumb tris...@trstn.net
---
diff --git a/babeld/Makefile b/babeld/Makefile
index e939310..70fcd64 100644
--- a/babeld
