1 of 1 people found this helpful
Hi Kyle, Yes it's normal starting BladeLogic 8.2 SP1 where we introduced the new version of Shavlik SDK 8.0. The scan basically appends to the same trace.txt file, so you never loose the history of previous scans. We're actually working with engineering to have the rolling mechanism for Trace.txt file, and we will also plan to move it from C drive to the RSCD_DIR folder. All of this is coming in the future - no ETA at this time. As for now, if you are pressed on space, just delete the Trace.txt file.
Is there an RFE #?
Yes, here's the Defect that addresses both issues:
QM001769290 - Create the shavlik analysis log file (Trace.txt) in RSCD tmp directory
This is scheduled for 8.5 - it's to move the trace.txt to RSCD_DIR and to incorporate rolling mechanism so that the file does not get out of control
Has there been any update on this?
is there no other way of either rolling or limiting the size of these?
not sure since which version of the agent this is the case, but at least for the 8.3 SP2 RSCD agent, no Trace.txt at all is generated/left behind on a target server.
You can only generate by manually executing BLPatchCheck2.
As Lazar has mentioned above, this places the file in RSCD_DIR\tmp now as well.
As i said, this might be the case for earlier versions of BSA as well.