e correct user?
>
> Thanks,
> David
>
> -Original Message-
> From: Parker, David K
> Sent: Tuesday, January 28, 2003 4:21 PM
> To: 'John DeCarlo'; Parker, David K
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: [Mailman-Users] Upgrade from 2.0x
>I've done as you suggested but I keep getting the following messages every
>few minutes:
>
>Subject: Cron /usr/bin/python -S /var/mailman/cron/qrunner
>Body: /usr/bin/python: can't open file '/var/mailman/cron/qrunner'
What are the persmissionf for /var/mailman/cron/qrunner? Does the file
exist
2003 4:21 PM
To: 'John DeCarlo'; Parker, David K
Cc: '[EMAIL PROTECTED]'
Subject: RE: [Mailman-Users] Upgrade from 2.0x to 2.1
I've done as you suggested but I keep getting the following messages every
few minutes:
Subject: Cron /usr/bin/python -S /var/mailman/cron
S /var/mailman/cron/nightly_gzip
Thanks,
David
-Original Message-
From: John DeCarlo [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 8:22 AM
To: Parker, David K
Cc: '[EMAIL PROTECTED]'
Subject: Re: [Mailman-Users] Upgrade from 2.0x to 2.1
David,
This will get your cr
David,
This will get your cron jobs reset.
Remember, they are running as user 'mailman'.
as root or mailman user, run:
crontab -u mailman -r
crontab -u mailman mailman_dir/cron/crontab.in
The first command will remove all the mailman cron jobs.
The second will put in just the 2.1 cron jobs.
N
I'm getting errors generated after upgrading from 2.0x to 2.1. I think its
related to Cfron jobs being scheduled to run. Both installs of Mailman were
done via RPM. I'm guessing that the latest RPM didn't take care of the Cron
jobs? Any hints on cleaning this up? I've been through the UPGRADE doc.
