Steve Burling wrote:
>
>Now that our upgrade/migration of Mailman has settled down, I've noticed 
>from my nightly 'mmdsr' run that data/pending.pck is just sitting there, 
>unchanging.  The last change date on the file is the date of our migration, 
>so I have two questions:
>
>    1) What's it used for?
>    2) Can I safely delete this copy, assuming that it'll get re-created
>       as necessary?


>From the NEWS file for 2.1.5

 - The pending database has been changed from a global pickle file, to a
   unique pickle file per mailing list.

i.e. in 2.1.5 data/pending.pck was deprecated in favor of individual
lists/listname/pending.pck files.

It held information about pending requests such as subscribe and change
of address that were waiting confirmation. It also has the information
about held posts that can be discarded or approved via 'confirm'.

When you send a "confirm xxxxxxxxx" command to listname-request or go
to the web confirm/xxxxxxxxx page, pending.pck is where the xxxxxxxxx
token is looked up to se what's being confirmed.

Pending.pck is not used for admindb requests. Those are kept in
lists/listname/request.pck.

Assuming you upgraded to 2.1.5 or later, your data/pending.pck was
converted to individual lists/listname/pending.pck files and can be
deleted as it is no longer used. Even if it wasn't converted by your
upgrade process, it can still be deleted as all the requests in it
have expired by now.

-- 
Mark Sapiro <[EMAIL PROTECTED]>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&amp;file=faq01.027.htp

Reply via email to