From: Olivier M. <om...@ti...> - 2007-05-25 13:41:38
|
> Setting correct home directory is very important for firebird > operation, cause here it keeps various lock files, and the fact > that only one firebird instance works with same set of lock files > at a time is absolutely required for it's successful operation. I > repeat this well known fact here to emphasize that starting more > then one instance from same working directory is a bug. (There is a > switch to set path to lock files separately from home, but this is > not a full-featured solution and requires more modifications in > firebird be useful, cause code, working with security database > ignores that switch, and opening database from more then one > instance of firebird breaks it at once - and this is just the first > sample which came to my mind.) Known and agreed. That's why this feature (ability to run multiple 'instances' from a same set of binaries - let's call this from a 'same home') would be welcomed by hosting providers. > Therefore currently we should better follow the rule of thumb - > separate home for each instance. But with that fact taken into an > account, it becomes clear that adding any more switches to command > line is senseless and is just duplication - separate home directory > contains separate config file. ** If ** the -e switch is made available on Win builds too, then at least playing at separating full copies in different directory trees would be appreciated, indeed. Side question, just for my education: why can't FB get rid of file- system based lock files? Why not only rely on named IPC objects? -- Olivier Mascia |