-----BEGIN PGP SIGNED MESSAGE-----
Marco Bizzarri wrote:
> On Wed, Feb 18, 2009 at 12:00 PM, Chris Withers <ch...@simplistix.co.uk>
>> Chris Withers wrote:
>>> ImportError: /usr/lib/zope2.9/lib/python/persistent/cPersistence.so:
>>> undefined symbol: PyUnicodeUCS4_AsEncodedString
>>> ImportError: /opt/Zope-2.9/lib/python/persistent/cPersistence.so:
>>> undefined symbol: PyUnicodeUCS2_AsEncodedString
>> Having had a bit of a google, I found this post from Andreas:
>> So it seems that "python2.4" resolves to one python when cron is running
>> and another when run from a shell of the same user.
>> Has anyone seen this behaviour before or know what could cause it?
>> PS: I've solved this for now by changing python2.4 to
>> /usr/local/bin/python2.4 in the control scripts, which seems to have
>> done the trick.
>> Simplistix - Content Management, Zope & Python Consulting
>> - http://www.simplistix.co.uk
> Is it possible that you've something in your .bash_profile or .bashrc
> which manipulates the PATH environment variable?
> The behaviour could be explained because cron could define and execute
> your script using /bin/sh as the shell. Even though that one is a sym
> or an hard link to /bin/bash, bash could behave like sh and not
> reading the .bashrc or .bash_profile scripts before starting.
Yup. In fact, this is why battle-scarred sysadmins always use
fully-qualified paths in scripts meant to be run from cron, as well as
in the crontab itself.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -