There's been extensive conversation about this over at

We would welcome your cron knowledge over there, straightening out this issue on either the Poormanscron side or the Chaos tools side.



Dave Reid’s picture

Sounds like an odd cron bug. Have you tried the 6.x-2.0 version of Poormanscron? Saw a report or two of people using it and the bug going away, so it's worth a try.

Dave Reid’s picture

Status: Active » Postponed (maintainer needs more info)