18.02.2015 15:46, liviusliv...@poczta.onet.pl wrote: >>> 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? > 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.
You confused port number with name of IPC object used in XNET. They are different and not related to each other. There is no way for client to specify non-default IPC name in connection string. Only possibility is to change IpcName at firebird.conf and make sure client used correct firebird.conf. With INET (TCP\IP) protocol it is much more easy - port number could be set in connection string. > P.S. > What about FB tools (gsec, isql...) - all use TCP? They all use what was specified in connection string. Regards, Vlad ------------------------------------------------------------------------------ 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
