Thank you for your email sent to [email protected]

Please be aware that we will only be respond to emails to this address if you 
have purchased a Support option which includes Priority Email Support.

Should you not have valid Priority Email Support then your email will be 
returned to you and you will need to resubmit it to the 
[email protected] email address.

For more details please refer to our web site support page 
http://www.omniaccounts.co.za/support. 


Kind Regards

The Omni Support Team


-----Original Message-----
From: [email protected]
Sent: Wednesday, 29 January 2014 2:37 PM
To: [email protected]
Subject: Re: [Firebird-devel] fb3 access modes under windows

On Wednesday 29 January 2014 15:03:02 Vlad Khorsun wrote:
> > But the questions will be asked - how can we run SC under FB3?
>
>     Isn't it was explained when shared page cache was committed ? 

Possibly - but I don't think it has been fully documented since then. I'm just 
an ordinary clueless user who blunders about, reading as little documentation 
as possible, trying whatever combination that works. :-)


>     Well, to run SuperClassic you should:
>
> a) set in firebird.conf
>
>     SharedDatabase = true
>     SharedCache = false
>
> and
>
> b) run listener in threaded mode
>
>     firebird -m [-a]
>
> > and does it make any sense?


Yes, that works.


One of the problems here is that the -m switch needs to be documented better 
(there are other problems with the -m switch, but documentation is the 
biggest.)

Basically this:

 instsvc i

installs firebird to run with the -m switch

and this:

  instsvc i -c 

installs it to run without the -m switch. 

Subsequent behaviour then depends on the configuration of firebird.conf, but 
there is no mention in firebird.conf as to how the two SharedNNNNN switches 
interact with -m

So this line

# SharedCache  SharedDatabase  Mode
# false        true            Classic with shared access // traditional CS/SC

is entirely dependant upon the -m switch, or lack of it to launch either CS or 
SC.

I guess what we really need is to document in firebird.conf how the -m switch 
affects the other two settings. There would seem to be a total of eight 
combinations.

Perhaps we need something like this:

# SharedCache SharedDatabase -m   Mode
# false       false           -   CS single attach only
# false       false           *   ????
# false       true            -   Classic with shared access
# false       true            *   SuperClassic with shared access 
# true        false           -   ?????
# true        false           *   Super with exclusive access
# true        true            -   Super with shared access - illegal in A2 :-)
# true        true            *   Super with shared access - also illegal



Paul
-- 
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird

------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to