I don't think this is a bug, certainly not a ClamWin portable one, but I thought I'd point it out anyway.
I'm using an old 64 Mb USB drive (I know, I know, but I never throw out anything) with just ClamWin Portable on it, no PortableApps menu. When I updated to 0.93.1, I noticed that the installed folder was using ~45 Mb on the stick, ~32 Mb of it being the main.cld file.
Just for the heck of it, I deleted the content of the ClamWinPortable\Data\db folder and ran ClamWin again. It properly detected that I had no definition files and once the update process was completed, I had a lean ~14 Mb main.cvd.
Update report list the same number of installed sigs.
Smaller main.cld:
main.cvd updated (version: 47, sigs: 312304, f-level: 31, builder: sven)
daily.cvd updated (version: 7570, sigs: 17115, f-level: 31, builder: neo)
Database updated (329419 signatures) from database.clamav.net (IP: 208.70.244.158)
Larger main.cld:
main.cld is up to date (version: 47, sigs: 312304, f-level: 31, builder: sven)
daily.cvd is up to date (version: 7569, sigs: 17094, f-level: 31, builder: ccordes)
Looks like the db is not optimized after each update. I don't know if it has an impact on scan speed...
What's the behavior of the ClamWin Portable installer? Should it wipe the db at every upgrade?
Just my 2 cents (canadian, not that bad at the moment...)
Simon
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I never thought about that.
Mine is 31 mb.
Ill look into this.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
I meant to make a post about this after the recent main update but forgot.
When the main data base updates it now as the ability to do a "delta" update, that is it adds the new stuff to the old. This makes for a smaller "download" of the update.
But it is not very efficient space wise. The compact main.cvd becomes a very large main.cld.
This is the same thing that happens with the daily.
daily.cvd is smaller than daily.cld.
If you have access to high speed internet access at the time the main data base updates you should delete the Main and the daily. Clam will then download a fresh, compact main.cvd and daily.cvd. Of course the daily.cvd will become a daily.cld on the next daily update.
Tim
Things have got to get better, they can't get worse, or can they?
Too bad one cant compact it like one can compact Thunderbirds mail files.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Just took a look and besides the increase in size of the daily and main, my drive has several .clamtmp files in the db folder, dating back as far as 03/18/2008. The biggest one is a 22.4MB from 05/06/2008 and here are the particulars:
File: clamav-7e712e0166ba1ed18b73b959c71031f2.00000c68.clamtmp, composed of
COPYING - 18 KB
main.db - 4625 KB
main.fp - 4 KB
main.hdb - 643 KB
main.mdb - 3505 KB
main.ndb - 14235 KB
main.zmd - 1 KB
Has anybody seen these .clamtmp files before? I wonder if these are created whenever ClamWin encounters a server problem while downloading updates.
they are remains of unsuccessful updates.
The only thing you should have in:
ClamWinPortable\Data\db
is:
mirrors.dat
main.cvd [or main.cld]
daily.cvd [or daily.cld]
you may/should delete the rest.
I delete them whenever CWP has a problem updating before I try again.
Tim
Things have got to get better, they can't get worse, or can they?
That's great info to know!
Is this temp file issue affecting others? If so, we could have the installer delete them since they're not of interest after the failed attempt. Or the launcher if it can't be resumed on each launch.
Sometimes, the impossible can become possible, if you're awesome!
I can't tell you if it's affecting many others but it does occur on all my CWP installations. It happens most of the time after an update failure.
It would be great if the launcher could get rid of them if it were not too difficult and doesn't mess up any other functions of CWP.
Is this something I should have brought to your attention,
If so, sorry, I thought it had been mentioned in someway in the past.
Tim
Things have got to get better, they can't get worse, or can they?
I have 2 USB drives (1 GB PNY Attache & 4 GB MicroCenter cheapie) with PortableApps installed and they both have .clamtmp files in the ClamWin db folder.
then at least the updates to the program, if it could completely overwrite the old database.
Don't be an uberPr∅. They are stinky.
have the installer or better the Launcher delete the folders. I had 8 of these clamtemp folder but I dont know their size cause I deleted them yesterday.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Until now I deleted those tmp files/directories manually. I'd appreciate if the launcher could do that for me.
I forgot to mention the .clamtmp folders in my initial post, but I had some of these myself. The date stamp was so old, I just deleted them straight away.
Glad to see others found this behavior strange/inconvenient.
Simon
What about the clamwin.zip file in the *:\PortableApps\ClamWinPortable\App\clamwin\lib folder? Where does it come from and can it be deleted? Mine has a date of 6/18 and contains many .pyo files.
Ed
Do Not delete it,
It is part of the ClamWin program
As with most of our apps, anything under:
x:\path to\ThePortableApp\App\
should not be touched unless you know what you are going.
Tim
Things have got to get better, they can't get worse, or can they?