[RESOLVED] QuickHeal Firewall log file fragmantation problem

[Pradeep1210]

I have QuickHeal Total Security installed on our systems. The QuickHeal firewall bundled with it seems to be too active on my system. It is constantly writing to the log files.

Just within one hour after full defrag of my C drive, I see that the fragmentation of this file has crossed 1700 fragments and still increasing:
C:\Program Files\Quick Heal\Quick Heal Firewall Pro\log\op_mon.log

This file is always on the topmost when I sort the list by number of fragments. Probably this is the real cause of pathetic performance of my PC.

1. Is anyone else experiencing the same problem?
2. What could be done for this?

I was wondering if anyone could point me to any (free) tool which can help me place the file in some location of the disk where I have a lot of unused free space, so that when the filesize increases it doesn't cause fragmentation.

[Nightwalker83]

Which operating system are you using?

[Pradeep1210]

Windows XP

[Nightwalker83]

Have you tried downloading the updates from the website?

[Pradeep1210]

Yes I already have the latest version.

[Nightwalker83]

Have you looked in the Technical FAQ and contacted their technical support?

[Pradeep1210]

It looks like that was some temporary unusual activity. Maybe there was something bad going on in my PC.

Today I again defragmented the drive in the morning, but I don't see that file in the fragmented files list any longer (about 9 hours gone by). The highest fragmented file I see is still of QuickHeal Firewall though:
C:\Program Files\Quick Heal\Quick Heal Firewall Pro\log\netstat4.log (46 fragments).

So I don't know how or why it was happening or how it got resolved. But the final thing is the problem is resolved

[Nightwalker83]

So I don't know how or why it was happening or how it got resolved. But the final thing is the problem is resolved

Maybe it was a file that was used by the program on the first run only?

[Pradeep1210]

I think when I defragmented yesterday, the file got placed at a good location either by chance or by defragmenter's intelligence, since I don't see that file anywhere now in the fragmented files list.

The other reason could be that there was some unusual network activity on my PC which caused the firewall to become more sensitive and act weirdly.