On 05/14/2010 12:59 PM, Christian Kastner wrote: > Hi Robbert, > > On 05/14/2010 11:59 AM, Robbert Kouprie wrote: >> On two different machines I have some cron jobs failing after upgrading from >> 3.0pl1-105 to 3.0pl1-110. Involved MTA is postfix in both cases. Downgrading >> to 3.0pl1-105 makes the issue go away again. >> >> For example, the below cronjob normally executes without output, within 1-2 >> seconds. >> >> # m h dom mon dow command >> */2 * * * * /usr/bin/fetchmail -s >/dev/null 2>&1
> First, I tested the above with some random commands, and they ran fine. > I then installed fetchmail. Checking fetchmail(1) however, I found this > for exit code 1: > > <quote code="1"> > There was no mail awaiting retrieval. (There may have been old mail > still on the server but not selected for retrieval.) If you do not want > "no mail" to be an error condition (for instance, for cron jobs), use a > POSIX-compliant shell and add > > || [ $? -eq 1 ] > > to the end of the fetchmail command line, note that this leaves 0 > untouched, maps 1 to 0, and maps all other codes to 1. See also item #C8 > in the FAQ. > </quote> One thing that just came to mind: If cron generated mails, that would probably screw up your testing. Say that -110 generates a mail. You downgrade to -105; -105 runs fine (because it gets the mail from -110). You upgrade to -110 again, and that fails again because of no mail. And so on. Could this be the case? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
