>> Thanks to Vlad and Alex the 2.5.2 snapshot from today (Oct. 17th) works >> fine so far from a Trace API POV. ;-) > > Thanks for confirmation :) > >> One question though, which isn't specific to the 2.5.2 snapshot. I've >> seen that the various fb_trace* files in e.g. c:\programdata\firebird >> aren't cleaned up. While they do as long as no trace data has been >> produced, they won't be cleaned up once there was trace data for the >> particular session, even if the trace session is stopped properly. > > Trace files could be not deleted only if Firebird was not shutted down > properly. This is specific Windows issue and we plan to adress it in the > future.
Ah, ok. This explains it well. The outstanding fb_trace* files are those from the 2.5.1 server, which crashed. Thanks, Thomas ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
