I get Mailman job logs that look like this:
Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/checkdbs^M) Sep 1 09:00:01 {my_node} CROND[30120]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/disabled^M) Sep 1 12:00:01 {my_node} atronus CROND[32514]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/senddigests^M) Sep 1 05:00:01 {my-node} CROND[2654]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/mailpasswds^M)
Where does the '^M' come from, and is it bad that it's there?
On 09/01/2015 10:00 AM, Steve Matzura wrote:
It's a <CR>. Your Mailman crontab file is a MS-Dos format file with <CR><LF> line endings instead of *nix format with <LF> line endings.
If your crons run OK, it's not a real problem, but if it were me, I'd fix the crontab file.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 09/01/2015 10:00 AM, Steve Matzura wrote:
It's a <CR>. Your Mailman crontab file is a MS-Dos format file with <CR><LF> line endings instead of *nix format with <LF> line endings.
If your crons run OK, it's not a real problem, but if it were me, I'd fix the crontab file.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Steve Matzura