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
It shall be possible either to disable the firebird.log, or to redirect it to another place/another filename,
by specifying this in the firebird.conf.
The search rule for the firebird.conf shall be:
1. Directory where the Client-DLL is found and loaded
2. Current directory (?)
Explanation:
For servers, typically, all log entries are written to "firebird.log" into the fbserver home directory.
Ok so far.
But client applications running on the same machine does also write into the firebird.log located on servers home directoy; this happens also if the client application does (DB-)connect to a complete other machine.
This results in a very confusing mix of server- and client-sourced log entries, especially if more than one client application is writing to the same firebird.log.
If no server installation exists (better to say: no registry entry is found), then the Client-DLL writes the firebird.log to the current directory, which may be (by accident) at any place on the machine.
The text was updated successfully, but these errors were encountered:
Submitted by: ohenri (ohenri)
Votes: 4
It shall be possible either to disable the firebird.log, or to redirect it to another place/another filename,
by specifying this in the firebird.conf.
The search rule for the firebird.conf shall be:
1. Directory where the Client-DLL is found and loaded
2. Current directory (?)
Explanation:
For servers, typically, all log entries are written to "firebird.log" into the fbserver home directory.
Ok so far.
But client applications running on the same machine does also write into the firebird.log located on servers home directoy; this happens also if the client application does (DB-)connect to a complete other machine.
This results in a very confusing mix of server- and client-sourced log entries, especially if more than one client application is writing to the same firebird.log.
If no server installation exists (better to say: no registry entry is found), then the Client-DLL writes the firebird.log to the current directory, which may be (by accident) at any place on the machine.
The text was updated successfully, but these errors were encountered: