Netpush file growing wildly

[sub]

It's been set at zero for many, many reboots, I've had that setting in there a while. I put it in when there were problems like this before with other users of the DCR-2650 getting 0 byte recordings, and when those were fixed, I just changed the setting from 1 to 0 rather than delete the key (so I could turn it back on easier if needed). It was only when I recently had a recording getting no data while I was at the machine and saw the "You are running out of space on C:" message that I realized it was still being written.

If you delete the registry setting entirely, and reboot, does it stop creating the file?

[ttfitz]

If you delete the registry setting entirely, and reboot, does it stop creating the file?

Didn't even require a reboot, I deleted the setting, tried recording something, no file. Put the setting back in (with 0 value), started recording, file created.

Took the key out again.

[sub]

Odd.

Yeah, just delete the setting.

[sub]

Ah, I see why it's creating it when the registry setting is present but set to zero. I've fixed it for the next release.

[ttfitz]

I definitely will not be doing anything to limit these log files that are only created with these special registry settings. They're only debug files, and user should not have enabled in normal use. They'll do more than just create big files - they will hurt performance. These need to be disabled unless looking into specific problems.

Fair enough.

So any thoughts on the error that caused the huge file to occur?

[sub]

I don't know. It looks like the socket was in use or something, or firewall software disallowed access. Hard to tell really. If it's repeatable, then there are probably other steps we could go through to work out what exactly is happening.