Arno Brinkman wrote:

>
> LockFile can be set in configuration and fb_lock_print use that one too.
> Also the lock-filename can be passed with fb_lock_print, so i don't see problems here?

A single fb_lock_print executable cannot handle different versions of
the lock tables. Would you suggest to name it fb_lock_print10,
fb_lock_print11 etc and deliver along with the appropriate engine providers?


Dmitry