You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
One error was due to the reason, fixed in related CORE4219.
Next is fixed here - they happened because FB3 config sorted config keys in ABC order, which is wrong for trace config files.
Submitted by: @mrotteveel
Relate to CORE4219
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.
Commits: b84835d FirebirdSQL/fbt-repository@927084b
The text was updated successfully, but these errors were encountered: