Glst on windows had a problem when its db size becomed larger than 10mb approximatively. So to reduce it's size, I implemented the script bellow, and programmed = its execution once a day (task scheduler) (once a day because of the number of mail we receive, we are an isp = ....) This script not only reduce glst db size, but archive glst-lame (for = future spammers.tab file regular integration or equivalent filter) and reset = its size to empty. Doing so, I never had any more problem with glst database size. (I never tried again if last glst currently running corrected the = problem, but as my 'cleanup' works, why trying now to get in trouble :) )
Francis ************************** @echo off C: cd \XMailTools\glst rem ** Be sure to stop xmail to avoid glst execution net stop xmail rem ** Now do a cleanup agains database glst --cleanup rem ** Now reduce glst database size rem - Delete old glst dump txt file del glst.txt Rem - Do a dump dbdump --dbfile glst.dbm --output glst.txt Rem - Delete glst database del glst.dbm Rem - Recreate glst database using old cleaned dump dbload --dbfile glst.dbm --input glst.txt rem ** Now add glst-lame content to archive (future use) Rem - Delete old glst-lame dump txt file del glst-lame.tmp Rem - Do a dump dbdump --dbfile glst-lame.dbm --output glst-lame.tmp Rem - Clear glst-lame (glst will recreate an empty automaticaly) del glst-lame.dbm Rem - Now add last content to archive copy glst-lame.txt + glst-lame.tmp glst-lame.txt Rem ** All done, restart xmail net start xmail ************************** >-----Message d'origine----- >De : [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] la part de Tracy >Envoy=E9 : jeudi 15 mars 2007 13:56 >=C0 : [email protected] >Objet : [xmail] Re: Question about GLST > > >Francesco Vertova wrote: >> At 13.10 15/03/07, you wrote: >>=20 >>> I'm currently using GLST with Xmail 1.24, and I've noticed that the >>> glst.dbm file never seems to shrink. The glst-lame.dbm=20 >grows each time I >>> do glst --cleanup, but the glst.dbm file only gets larger. >>=20 >> I think glst.dbm is supposed to grow and grow until you perform a=20 >> manual compact (dbdump --dbfile glst.dbm | dbload --dbfile=20 >> compact.dbm), even though every --cleanup frees up some space that,=20 >> according to the gdbm doc, should be re-used (so, all things equal,=20 >> the growth rate should decrease over time). > >Well, see, that's the weird thing. When I do a glst --cleanup, the=20 >glst.dbm file actually *grows* (admittedly, only a small=20 >amount - maybe=20 >10 - 20 KB or so). Which I thought was weird. > >> No idea how the glst.dbm size may affect performance. It has been=20 >> reported that (on Windows) the file may get corrupted (becoming huge = >> with glst using a lot of cpu) unless you compact it from time to=20 >> time. On my (lightweight) Windows server glst.dbm is slowly growing=20 >> above 1Mb, with no apparent performance hits. I've compacted it a=20 >> couple of times in the past, though. > >Well, mine is nowhere near that size, but on the other hand, I'm only=20 >supporting a user base of maybe 15 people, with a total of perhaps 40=20 >(valid) email addresses. (I say "valid" because I also have a spamtrap = >address collection, but they all feed into a single email address). >- >To unsubscribe from this list: send the line "unsubscribe xmail" in >the body of a message to [EMAIL PROTECTED] >For general help: send the line "help" in the body of a message to >[EMAIL PROTECTED] > - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
