Re: [mv] VERY large session.gdbm

[kyle <invisio@abac.com>]

I run mv 3.12

When I run expire, the -c arg does not seem to work 
(no compaction)

So I have to run the compact program
(in mv /bin dir) it takes the path to the db directory.

example (freebsd) change to the catalog dir (where your 
.db or .gdbm database lives) then issue:

/full/path/to/mv/bin/compact ./

(as minivend user/same as daemon user)

If you do that after an expire, it will greatly reduce the size
(as long as you don't have unusually high session expire times)

Kyle (KC)


At 11:55 AM 12/5/00 , you wrote:
>Running MV 3.14
>
>Although I run expireall -r as minivend from crontab each day, the
>session.gdbm for one of my catalogs has become huge!
>
>I've ran "expire -r -c catalogname" as minivend from the command line and
>after a long wait, receive a lengthly error message which I'll paste below.
>
>Can I simply delete the session.gdbm (and then replace it by "touch")
>without causing any problems or does anyone know how I can force it to
>expire?
>
>Thanks!
>


_______________________________________________
Minivend-users mailing list
Minivend-users@minivend.com
http://lists.akopia.com/mailman/listinfo/minivend-users