On Wed, Aug 8, 2012 at 5:21 PM, Roberto Riggio <[email protected]> wrote: > Wouldn't this imply that iperf will start in any case? Uhm, I thought that would need a "/etc/init.d/iperf enable" to be run in the first place. So that simply "opkg install"ing the package wouldn't make it start at every boot.
> This is probably not something > I would would want as default behavior (am I alone on this?). Definitely, I wouldn't want that neither. On Wed, Aug 8, 2012 at 5:24 PM, Luka Perkov <[email protected]> wrote: > On Wed, Aug 08, 2012 at 05:02:30PM -0300, Gui Iribarren wrote: >> Starts iperf in server mode as a daemon, with IPv4 + IPv6 support enabled >> (-V) > > Can you change your patch so the script instalation is optional and > disabled by default? Something like we have fw_setenv in uboot-envtools > package. Could do, but i haven't seen other daemons take this approach: two packages i can recall right now are aiccu and nodogsplash, both of them include a "START=xx" in the init.d script, but that doesn't take into effect until you "enable" them after opkg install They do "enable" themselves (per definition) if you include them as precompiled packages in the firmware binary, but that's a whole differt story :) _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
