Other than, do not write to a trace file directly from a DriverSet, not really. A trace from the DriverSet is not useful for anything, other than filling disks, because driver data get interleaved in a way that cannot be analyzed reliably, so traces should always be written directly to a file on a per-driver basis.
-- Good luck.
If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...
lhaeger;276475 Wrote: > kbuley wrote: > > > Any ideas? > > Post it again tomorrow... > > > No April Fools... the file looks like someone started dxcmd and just > held down enter. (and how is anything from dxcmd getting in to that > file)
On 01.04.17 18:25, ab wrote: > Other than, do not write to a trace file directly from a DriverSet, not > really. A trace from the DriverSet is not useful for anything, other than > filling disks, because driver data get interleaved in a way that cannot be > analyzed reliably, so traces should always be written directly to a file > on a per-driver basis.
And figuring out why your driverset jobs doesn't work ...
ndsmanage stopall works, and is the only way to release the handle on the file so that it can be deleted... but it doesn't answer the question why that file will randomly start filling up with what looks like the output of someone launching dxcmd and holding down enter. I haven't been able to make any correlations to any other events... sometimes it will be fine for weeks, sometimes it loses its mind several times in a day.