recursor fails to restart with old config setting nofork=yes

[anon]

Changeset 1518 removed the nofork option.

A Fedora user reported ( https://bugzilla.redhat.com/578825) that this broke his upgrade from 3.1 to 3.2. His configfile still contained the nofork=yes setting. The update restarts the recursor, but this fails with 'Exception: Trying to set unexisting parameter 'fork.

It would be great if the nofork parameter could just be ignored instead.

The best solution would be a configtest option, so we can conditionally restart only if the config is correct, but this is probably more work.

Thanks,

Ruben

[ahu]

While I appreciate the sentiment, this would lead to heaps of configuration items silently being ignored..