[Olsr-dev] Make deprecated options issue a warning

Jo-Philipp Wich (spam-protected)
Tue Aug 19 18:38:24 CEST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Guys,

we're trying to support both v0.5.5 and v0.5.6 here and so far its a major problem that
OLSRd refuses to start when there are deprecated options in the configuration file.

Is it possible that those options present in v0.5.5 but not in v0.5.6 generate a warning
upon OLSR startup, so that legacy configurations continue to work? That would ease the
transition to the newest version a lot.


Greetings,
JoW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIqvcAdputYINPTPMRAvIOAKCb1XWF8VKKT2P6ugewqHrWnQONpACgpXZz
wb8khpA+AWL9nvHsqTbL4UQ=
=x8Eu
-----END PGP SIGNATURE-----




More information about the Olsr-dev mailing list