-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
For your other questions: stderr and stdout are
buffered by sge
because they are send over network. At the toolserver configuration
it is send to localhost by default because all execution servers
have the same filesystems mounted. At a standard cluster
configuration out/err files are written on submit host instead.
So would the hint given by Platonides before (btw.: thanks a lot for
this!) be of any help?
On 12.06.2012 22:48, Platonides wrote:
That looks like line buffering in stdio. You can try
prepending the
python command with: stderr -e0
(despite the fact that stderr should be unbuffered by default...)
I'm unsure if it's being buffered at python or if SGE is doing
caching there, thoguh. It _should_ be simply passing the file
descriptor but, who knows?
be of any help? Either to get SGE to behave like python? Or vice-versa?
PS:: qcronsub does not output anything if the job was
submitted
succesfully and all resources are requested correctly. So no need
to send the output to /dev/null.
;)) thanks for the hint; I cannot rember but there HAS TO BE a reson why
I finally decided to add '> /dev/null' ... might be just 1 line droped
by SGE or something like that... will check that sometime!! tks! :)
Greetings and thanks for all the hints!
DrTrigon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAk/d1DUACgkQAXWvBxzBrDA1cQCffjfkx3YY5vglnLHcvXVBXVyK
dBUAnRcEP4pZbgpdBSFwaPIJBFGLUu2r
=xpXm
-----END PGP SIGNATURE-----