* Felix Fietkau [09.06.2014 21:23]:
[...]
> For this trigger we can add a time delay, which will aggregate events.
> Once that is implemented correctly, 400 ifup events in rapid succession
> will lead to only one series of init script calls instead of 400.
> With that approach, such micro-optimi
On 2014-06-05 10:31, Bastian Bittorf wrote:
> i have a router here with 400 vlan-interfaces.
> i'am still not happy, that an hotplug-event triggers a lot of unneccesary
> action.
>
> i see at least 3 possibilities reduce the load:
> (beside the upcoming procd-interface job)
>
> 1)
> each script
* Weedy [06.06.2014 09:23]:
> On 5 Jun 2014 04:19, "Bastian Bittorf" wrote:
> > 3)
> > during bootup or '/etc/init.d/$daemon enable' we build a directory for
> > enabled scripts. while we are at it, we can e.g. call 'ifup'/$ACTION if the
> > daemon supports/implements it, otherwise ignore
>
> Yo
On 5 Jun 2014 04:19, "Bastian Bittorf" wrote:
>
> i have a router here with 400 vlan-interfaces.
> i'am still not happy, that an hotplug-event triggers a lot of unneccesary
action.
I wasn't paying attention but what services are you complaining about?
On my router things like dnsmasq, the firewa
On 5 Jun 2014 04:19, "Bastian Bittorf" wrote:
> 3)
> during bootup or '/etc/init.d/$daemon enable' we build a directory for
> enabled scripts. while we are at it, we can e.g. call 'ifup'/$ACTION if
the
> daemon supports/implements it, otherwise ignore
You mean the symlinks in /etc/rcS/?
_
i have a router here with 400 vlan-interfaces.
i'am still not happy, that an hotplug-event triggers a lot of unneccesary
action.
i see at least 3 possibilities reduce the load:
(beside the upcoming procd-interface job)
1)
each script implements something like:
#!/bin/sh
/etc/init.d/$daemon enab
