> Configuration fbtrace.conf contains syntax errors
> -------------------------------------------------
> 
>                 Key: CORE-4163
>                 URL: http://tracker.firebirdsql.org/browse/CORE-4163
>             Project: Firebird Core
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: 3.0 Alpha 1
>         Environment: Windows 8 64 bit
> WI-T3.0.0.30566 Firebird 3.0 Alpha 1 (64 bit)
>            Reporter: Mark Rotteveel
> 
> 
> Firebird.log contains errors when I change firebird conf to enable system 
> auditing with AuditTraceConfigFile = fbtrace.conf
> 
> RAMONA Sun Aug 04 15:13:20 2013
> Trace plugin fbtrace returned error on call trace_create.
> error while parsing trace configuration
> line 208: error while compiling regular expression 
> "%[\/](test|azk2|rulez).fdb"
> 
> The entry in the file is the one that is in the firebird 3 distribution:
> 
> # Enable logging for test.fdb, azk2.fdb and rulez.fdb in any directory
> # into log file name matching database name - test.log, azk2.log and 
> # rulez.log appropriately
> #
> database = %[\\/](test|azk2|rulez).fdb
> {
> enabled = true
> log_filename = \1.log
> }
> 
> Either the syntax used in the config file is wrong or the parser doesn't 
> process it correctly.

    In fb3 we switched trace config to use common code used to parse 
firebird.conf (and other)
config files. Unfortunately, this common code introduced (at least) two 
problems when used for 
the trace config :
1. it converts all repeated slashes into single slashes (and i do not know why 
it is necessary)
2. it sorts all parameters by names internally while trace configuration must 
be applied from top 
    section to bottom one (this one i already fixed in my private tree)

    So, the question is - is this really necessary for the 
ConfigFile::macroParse() to strip repeated
slashes. And, if yes, how to make workaround for the trace to deal with it.


Regards,
Vlad

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to