Crontab doens't run with the same environment as you, the user. In
particular the Python path will be different. Listen to the error
message; it's telling you the right thing.
Malcolm
--
Tolkien is hobbit-forming.
http://www.pointy-stick.com/blog/
I'm not going to give you a step-by-step way to fix this. As I said in
the original post, it's most like that cron's idea of the Python path
isn't what it needs to be. So look up how to set environment variables
in cron.
Malcolm
--
A clear conscience is usually the sign of a bad memory.
http://www.pointy-stick.com/blog/
--- Amit
* kevi...@gmail.com <kevi...@gmail.com> [2008-02-14 22:07 -0800]:
env -i path/to/script
This way you can test on the shell what goes wrong.
I do all the set up in .bashrc an and run the cron job like this:
0 * * * . $HOME/.bashrc; $HOME/.../script
HTH,
Thomas
kevi...@gmail.com schrieb: