Michael Hoffman <[email protected]> writes:
> Our system administrators recently upgraded our GridEngine
> installation to 6.2u5.
That seems an odd choice for an upgrade. There are several possible
regressions.
> Now I find that using %s in a qsub command line
> results in an immediate SIGSEGV. For example:
>
> $ qsub -b y -sync y echo %s
> Your job 1620936 ("echo") has been submitted
> Job 1620936 exited because of signal SIGSEGV
>
> This happens when I use -sync n as well, but it is easier to see the
> results this way. This works:
>
> $ qsub -b y -sync y echo %%s
> Your job 1620937 ("echo") has been submitted
> Job 1620937 exited with exit code 0.
>
> Unfortunately, the latter case does not escape the percent--it results
> in %%s being echoed, so I cannot simply replace "%s" in my scripts
> with "%%s."
What happens if it's quoted appropriately for a shell metacharacter
(presumably with two levels of quoting)?
> Do you know what causes this?
No, but /var/log/messages should tell you what SEGVed. I'm not sure
from the output whether it could be the SGE shepherd. I can't reproduce
it with recent code and tcsh anyhow.
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
