I should have mentioned this before...
One thing I did notice is that you will loose all pending administrative
tasks, but I'll bet you can use dumpdb to see which lists have pending
tasks.
On Tuesday, November 27, 2001, at 11:09 AM, Phydeaux wrote:
> Thanks!
>
> reb
>
> At 10:54 AM 11/27/200
At 10:38 AM 11/27/2001 -0500, Barry A. Warsaw wrote:
> P> Next, is there anything markedly different with v2.1 that would
> P> make this unworkable, unwise, or unnecessary?
>
>MM2.1 should have largely the same issues, except it'll have a long
>running daemon instead of cron-invoked qrunne
I posted this once before for backing up archives, dbs, and keeping all
user info, but it had one small bug. The files in archives/private/*
had the wrong permissions set. A small change took care of that. Also,
the $person_to_nag_with_700_emails variable doesn't matter if you use
the --out
> "P" == Phydeaux <[EMAIL PROTECTED]> writes:
P> Using bin/list_lists I can get a list of the lists. I can then
P> easily cycle through each list and (for each one) do the
P> following:
P> - Run bin/config_list - Run bin/list_members (once for
P> digested, once for regu
At 07:34 PM 11/26/2001 -0800, you wrote:
>At 21:49 -0500 11/26/2001, Phydeaux wrote:
>>Using bin/list_lists I can get a list of the lists. I can then easily cycle
>>through each list and (for each one) do the following:
>>
>>- Run bin/config_list
>>- Run bin/list_members (once for digested, once f
At 21:49 -0500 11/26/2001, Phydeaux wrote:
>Using bin/list_lists I can get a list of the lists. I can then easily cycle
>through each list and (for each one) do the following:
>
>- Run bin/config_list
>- Run bin/list_members (once for digested, once for regular members)
>- Copy the complete archiv
There have been questions here of late regarding backups.
Using bin/list_lists I can get a list of the lists. I can then easily cycle
through each list and (for each one) do the following:
- Run bin/config_list
- Run bin/list_members (once for digested, once for regular members)
- Copy the compl
