> 02.07.2012 17:22, Thomas Steinmaurer wrote: >> >> Is this expected when running a sweep not via gfix? > > It's expected when tracing all attachments indirectly utilized by > services.
Ok, but the log_sweep is a per-database trace setting and not exposed when using the services section of the trace configuration. The missing remote process information simply confuses my parser *g*, so either I need a way to reliably detect that the remote process information is available for the various SWEEP_* events or some kind of dummy line (perhaps there is some information available via the Services API) would make sense in the output to keep the output format the same, for both, sweep events issued by a gfix call or via the Services API. Thanks, Thomas ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
