[OLSR-users] Re: Segmentation fault about olsrd-0.4.9

[Andreas Tønnesen]

> another approach will be a date check of the *.so file against the
> executable with a warning prompt such as "Hell! Press Y-E-S to use that
> old
> stuff!"

:-D
Actually, I agree that olsrd itself should have a way to check
compability. The plugin interface version checked at plugin load was ment
to cover backwareds compabillity issues. But the problem here is rather
internal changes in olsrd, not updates in the plugin interface. But I
think perhaps we'll increase the plugin interface version for every
release so that olsrd will warn you about this at startup... perhaps using
your suggested warning Sven-Ola  ;-)

- Andreas

>
> Rgds,
> Sven-Ola
>
> "Thomas Lopatic" <(spam-protected)> schrieb im Newsbeitrag
> news:(spam-protected)
>>> Because when we ship a new release with my_plugin version 0.4 and the
>>> previous release contained my_plugin version 0.3 you will have:
>>> /usr/lib/olsrd_my_plugin.so.0.3
>>> /usr/lib/olsrd_my_plugin.so.0.4
>>> installed if make install implies make install_libs.
>>> Now, in the old configfile(which is the reason for the problems) there
>>> is
>>> an entry:
>>> loadplugin "olsrd_my_plugin.so.0.3"
>>> and so - the old plugin will still be loaded.
>>
>> Hmmm. What about the following approach: Shall we create a symbolic link
>> olsrd_my_plugin -> olsrd_my_plugin.so.0.4 and then use "olsrd_my_plugin"
>> in the configuration file? The "install" make target would then simply
>> remove the link and re-link to the latest version.
>>
>> -Thomas
>>
>> _______________________________________________
>> olsr-users mailing list
>> (spam-protected)
>> https://www.olsr.org/mailman/listinfo/olsr-users
>
>
> _______________________________________________
> olsr-users mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-users
>


---------
Andreas Tønnesen
http://www.olsr.org