[OLSR-users] OLSRD triggering too many modprobes

Andreas Tønnesen (spam-protected)
Mon Apr 17 20:38:05 CEST 2006


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.

- Andreas

Ignacio García Pérez wrote:

> Hi,
> 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 
> configuration.
> Any other suggestions?.
> Nacho.
> _______________________________________________
> olsr-users mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-users

More information about the Olsr-users mailing list