Hi,

> In Vulcan, we may have a few engine providers within a single
> installation. It's supposed that every of them is responsible for each
> own ODS. The problem is that each engine provider may have different
> (read: incompatible) lock manager implementation. As all providers by
> default share the same root directory (and hence the lock table), an
> attempt to use them simultaneously would cause server crashes and
> database corruptions. Am I missing something or is it a real problem? If
> the latter, how are we going to guarantee the consistency? Also, even if
> all engines are configured for different roots, this issue implies that
> one would need a few versions of fb_lock_print in order to analyze the
> lock table.
>
> Comments?

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?

Regards,
Arno Brinkman
ABVisie

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
General database development support:
http://www.databasedevelopmentforum.com

Firebird open source database (based on IB-OE) with many SQL-99 features :
http://www.firebirdsql.org
http://www.firebirdsql.info
http://www.fingerbird.de/
http://www.comunidade-firebird.org/

Support list for Firebird and Interbase users :
firebird-support@yahoogroups.com

Nederlandse firebird nieuwsgroep :
news://newsgroups.firebirdsql.info

--------------------------------------------------------------------------------
Mijn Postvak In wordt beschermd door SPAMfighter
1339 spam-mails zijn er tot op heden geblokkeerd.
Download de gratis SPAMfighter vandaag nog!