[OLSR-users] OLSRD triggering too many modprobes
Ignacio García Pérez
Tue Apr 18 10:03:25 CEST 2006
Andreas Tønnesen escribió:
> I've added two new keywords to the config file. One global:
> This option sets the interval, in seconds, that olsrd
> will check the configured
> interfaces for changes in configuration. Defaults to 2.5.
> And one pr. interface:
> AutoDetectChanges [yes|no]
> Olsrd can autodetect changes in interface configurations(
> polling on the inter-
> val set by NicChgsPollInt ). This is Enabled by default
> but can be turned off
> pr. NIC to save CPU cycles.
> This should be enough to help you out as far as I can see.
Thank you. I had already implemented the variable olsrd.conf file
solution. Seems to work fine. When a new interface is plugged in (USB
WiFi stick, for example), a new olsrd.conf file is generated and a HUP
signal is sent to the daemon so it re-reads the configuration and
reconfigures the interfaces.
HOWEVER, it is quite a dirty solution, since I have to first collect the
names of each interface and use sed to modify a temporary olsrd.conf
file. It would be MUCH easier if the olsrd configuration file format had
a "directory include" directive.
With your solution, I would just disable change detection and send a HUP
signal whenever a new network interface is plugged. However, this still
has a problem: when the olsrd daemon reconfigures, it will probe all
interfaces causing quite a lot of modprobes. Better than happening every
2.5 seconds, though. I think these configuration options are anyway
needed and may be useful in other situations.
> - Andreas
> Ignacio García Pérez wrote:
>> I just finally found out the responsible of the intermitent lockups
>> of my embedded systems.
>> It turns out that whenever olsrd checks for a network interface, a
>> kernel module loader event is triggered and modprobe is called.
>> Since I have like 12 "phantom" interfaces that are in the olsrd
>> configuration "just in case" some day they get plugged in, the 12
>> modprobe processes put a large load in the system periodically.
>> The only good way I could think of to solve this is to use a variable
>> olsrd.conf file which is updated whenever a new interface is plugged
>> and then issues a HUP signal so the olsrd daemon reloads the
>> Any other suggestions?.
>> olsr-users mailing list
> olsr-users mailing list
More information about the Olsr-users