On 02/18/15 16:46, [email protected] wrote: > Hi, > > > >>> So, you start two instances of Firebird server at the same time, correct >>> ? > yes - both on different port > >>> This message put by the second instance. If you stop both servers and >>> start >>> fb3 first, you'll have same message in fb2.5 log after you start fb2.5. >>> And error message confirms it, isn't is ? > It not only confirm but report error ;-) > > >>> To avoid this message you could start second instance with XNET disabled. >>> To do it, specify switch -i in command line. Of course, it will disable >>> local protocol for this instance. It is disabled in any case, btw, but you >>> can explicitly control which instance will run without XNET. > But why i should do this?
Because you use OS where not only TCP is supported to talk to firebird. > I run separate instances, inter process communication memory should be > different for both servers > and mutex name should contain port number to identify instance or something > like this. Mutex name is _absolutely_ unrelated with port number. > P.S. > What about FB tools (gsec, isql...) - all use TCP? > Yes, they do, and they also use XNET and WNET for windows. To be precise they have no idea what lower-level protocol is used to talk to the server, this may be even embedded connection - it's no difference for utilities. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
