Re: [Firebird-devel] Firebird 2.5 embedded. Shouldn't the tracing be off by default? Writing to C:\Programdata folder problem

[Liana S. <Lia...@ma...>]

Hello 
Thanks for the answer.
But the problem is since it is firebird embedded then it is being distributed to users.
They must then be able to run the program when for example they are domain users (on windows).
But the user can have write access problems to C:\ProgramData folder as one of our customers is experiencing.
Our program has to be able to work for domain users.
And the domain user is the least privileged user on the computer and is guaranteed access to %appdata% folder, but not to %programdata% folder.
Is it any possibily then to provide another folder for fb_trace* and fb_lock* files?
This is already second time I am experiencing problems with firebird not being compatible to windows requirements (also firebird.log is being written to a place where it is not accepted to write for designed to windows programs).

Please, what can we do to redirect writing to these folders?
Best regards

Liana E. G. Svendsen
Systemutvikler


-----Opprinnelig melding-----
Fra: Alex Peshkoff [mailto:pes...@ma...] 
Sendt: 19. november 2010 14:44
Til: fir...@li...
Emne: Re: [Firebird-devel] Firebird 2.5 embedded. Shouldn't the tracing be off by default?

 On 11/19/10 15:51, Liana Svendsen wrote:
> Hello
> I noticed that my firebird embedded is creating a lot of fb_trace* and fb_lock* files under C:\ProgramData\Firebird folder.
> Is it possible to turn off?
> I thought it shouldn't be by default on since in my firebird.conf it stays
>
> # ----------------------------
> # Trace configuration file for system audit
> #
> # Empty value means that system audit is turned off.
> #
> # Type: string
> #
> #AuditTraceConfigFile =
>
>
> And I don't have any fbtrace.conf file.

Let's start with fb_trace*. Setting in firebird.conf means only that
there is no system audit. But you may at any moment attach to trace
service and start to watch what does your server do. Shared memory files
fb_trace* are required to support it. If you talk about completely
turning off trace - suppose this can be done, but please explain what is
the need in it.

What about fb_lock* files - this is per-database replacement of previous
isc_lock1.$hostname file, which was located in firebird's root
directory. Placing them in single when known in OS place makes it
possible for a few instances of embedded server, located in different
places of dir's tree, safely work with same database. Having separate
file per database helps with performance when firebird works with >1
database. I suppose that removing this files is close to unreal.



------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel