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 u
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
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 -
