[Mailman-Users] /bin/sh: mailman: command not found

Dennis Putnam dap1 at bellsouth.net
Sun Jun 10 20:35:49 CEST 2012

Hi Mark,

I think I got it. I did a 'crontab -r -u mailman' which should have
removed the errant cronjob. I also deleted /etc/cron.d/mailman, edited
my additions to include the user 'mailman' then restarted mailman. The
new /etc/cron.d/mailman showed up again as expected and I think it will
be OK now. Maybe both cronjobs were running and the error message was
coming from the incorrect one. Thanks.

On 6/10/2012 12:31 PM, Mark Sapiro wrote:
> Dennis Putnam wrote:
>> Doh! You are correct. The directory /var/spool/cron is empty.
>> The format of the cron file is what was distributed with CentOS. Odd
>> that it would be wrong but explains why my additions work and the distro
>> ones do not. Is this file unchanged with updates so if I fix it, it
>> won't break?
> It is not wrong. It is correct for a system crontab, i.e. for
> /etc/cron.d/mailman. If the standard crons give the 'mailman command
> not found' message and your added entries work, the crontab is
> installed somewhere as a user crontab, not a system crontab.
> This is not consistent with what you are telling me you see in
> /etc/cron.d/mailman and /var/spool/cron so I don't know what's
> actually going on. Are you certain /var/spool/cron is empty?
> What's in /var/log/cron?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20120610/6b13ca2c/attachment.pgp>

More information about the Mailman-Users mailing list