Hmmm. I'd tried running a script similar to the one you've got below, but not out of tmp just to shorten the pathname. I tried running it out of tmp, but no dice. It might be something stupid but it leaves no logs (that I've found yet, anyway) and it really makes me scratch my head.

I ended up doing something like what you've got below, throwing it in a while loop with a sleep, and running IT as my cron daemon, carrying a few extra processes as extra baggage. I try not to think about it, but I can't stop.

Thanks! Dave Klingler

Could it be a pathnamelength problem? (Doesn't cron send any error mail or log any errors about what's going on?)

Try making /tmp/foo that has #!/bin/sh /usr/local/bin/python -S /storage/virtual/mydomain.net/home/mailman.cgi/cron/qrunner

making it executable, and putting *it* in the cron entry, just for grins.

Dave Klingler wrote:

...

Hi folks. I've noticed references in the docs to bug problems in the Redhat version of crond. I'm having strange problems with crond on my Redhat server (vixie cron), and I'm wondering whether anyone else has some insight to offer.

Basically this entry works:

• • • • * /usr/local/bin/python -S /home/mailman/cron/qrunner

But this one doesn't:

• • • • * /usr/local/bin/python -S /storage/virtual/mydomain.net/home/mailman.cgi/cron/qrunner

I'd been banging my head against this one for a while before I realized the cron entry wasn't running. The entries themselves are correct, but qrunner won't qrun.

TIA for any ideas! Dave Klingler

---

Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users

---

Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users