-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I've made a couple of changes to cronsub in response to some issues reported by
users. Specifically:
* cronsub now requires that the script file be executable, and will raise an
error if it's not. The previous behaviour was that non-executable scripts
would be executed by /bin/sh. If this affects you, the fix is to make the
script executable (chmod +x).
* Previously, SGE would copy the job script to a shared directory and execute
it there. For example, if you submitted $HOME/test.py, it would be copied
to a file such as /sge62/default/spool/wolfsbane/job_scripts/117333 before
starting. This was unfortunate for Python users who depended on Python's
behaviour of treating the script's directory as part of the "import" search
path.
This behaviour has been changed, so that the script file will be executed in
its original location.
I appreciate that the first item may be a breaking change for some users.
However, on balance this seems like the lesser evil.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk0ny8sACgkQIXd7fCuc5vK1UwCfaIt9gOSWym8sDOKR8bekuUaK
Qy4AoLLJIB1xaUjeKdpUHLZ6npg/0FiS
=VV97
-----END PGP SIGNATURE-----