Windows Firebird 3.0 system audit and directory macros in log_filename directive

[basid-irk]

firebird.conf:

AuditTraceConfigFile = "$(root)/audit.conf"

audit.conf:

services 
{
  enabled = true
  log_filename = "$(root)/audit-svc.log"
}

Run:

> "30/fbtracemgr" -user sysdba -se service_mgr -l -z
Firebird Trace Manager version WI-V3.0.13.33818 Firebird 3.0

Session ID: 1
  name:  Firebird Audit
  user:  SYSDBA
  date:  2025-07-24 12:29:32
  flags: active, admin, system, audit

but in firebird.log:

TEST64	Thu Jul 24 12:29:32 2025
	Trace plugin fbtrace returned error on call trace_create.
	error while parsing trace configuration
	line 41, element "log_filename": pattern is invalid
	 v:\db\30\audit-svc.log

On (windows) Firebird 4.0 and Firebird 5.0 directory macros for log_filename of system audit work fine.

[aafemt]

It is natural that old versions of software contain less features than new ones. Macros were not supported in trace config file that time.

[basid-irk]

log_filename = "$(root)/audit.conf" work fine with LI-V3.0.13.33818 Firebird 3.0. On Windows value v:\db\30\audit-svc.log interpeted as v:db30audit-svc.log (invalid filename).