kazaadebug: 315 Mb strong (& still growing). - P2P-Zone

spstn · 30-05-02, 01:04 AM

My HD available space was shrinking faster than I was able to account for & I started to fear the worst: my first virus ever. But then, after inventoryng my C drive I found the answer; kazaadebug.log had grown to 315 Mb in just 10 days (8000+ entries!)

I had learned about it in a post from Harbinger, I believe. I created the log file, run Kazaa Lite for a few minutes & then analized the entries and there it was: the proof that Kazaa was tying IP addresses to user names. After I had my fun I forgot about it, because the post said that the trick only worked if you started Kazaa from its folder and not from its shortcut.
So I continued using the program from its shortcut and guess what: the log kept growing fatter & meaner.

The moral: If you created the file, have your fun & then get rid of it; & if you have it and your HD is filling faster than it should that could be the reason.

butterfly_kisses · 30-05-02, 12:51 PM

lol, i had no idea...wow that is incredibly HUGE!

ssj4_android · 30-05-02, 03:33 PM

Good you found the problem. I had something simmilar. Except it was with a system log, I couldn't delete it normally, and he came back when I could delete it. I had to disable the logging, delete it, and make an empty write protected file in it's place.

30-05-02, 01:04 AM	#1
spstn No Nonsense Nonsense Join Date: May 2002 Location: Miami Posts: 382	kazaadebug: 315 Mb strong (& still growing). My HD available space was shrinking faster than I was able to account for & I started to fear the worst: my first virus ever. But then, after inventoryng my C drive I found the answer; kazaadebug.log had grown to 315 Mb in just 10 days (8000+ entries!) I had learned about it in a post from Harbinger, I believe. I created the log file, run Kazaa Lite for a few minutes & then analized the entries and there it was: the proof that Kazaa was tying IP addresses to user names. After I had my fun I forgot about it, because the post said that the trick only worked if you started Kazaa from its folder and not from its shortcut. So I continued using the program from its shortcut and guess what: the log kept growing fatter & meaner. The moral: If you created the file, have your fun & then get rid of it; & if you have it and your HD is filling faster than it should that could be the reason.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

30-05-02, 12:51 PM	#2
butterfly_kisses Napsterite Join Date: Apr 2002 Posts: 138	lol, i had no idea...wow that is incredibly HUGE!

30-05-02, 03:33 PM	#3
ssj4_android Redefining Reality Join Date: Feb 2002 Posts: 406	Good you found the problem. I had something simmilar. Except it was with a system log, I couldn't delete it normally, and he came back when I could delete it. I had to disable the logging, delete it, and make an empty write protected file in it's place.