IRAF shell script problems in Redhat FC2
Doug Mink wrote on Jan 10, 2006
We've been building instrument data reduction pipelines in CL
for quite a while and have been moving the top level to CL
scripts callable from the Unix command line so that we can
use multiple processors. Every thing works well under Solaris
and has moved pretty well between versions of IRAF, but
when we try to run working scripts under Linux (Redhat FC2),
they crash soon after entering any SPP program which is
called by the CL script. Functions such as lpar, dpar, dir, and
epar work, but as soon as you try to access a data file, the SPP
program and the script crash.
Does anyone have any ideas of what could be going wrong?
for quite a while and have been moving the top level to CL
scripts callable from the Unix command line so that we can
use multiple processors. Every thing works well under Solaris
and has moved pretty well between versions of IRAF, but
when we try to run working scripts under Linux (Redhat FC2),
they crash soon after entering any SPP program which is
called by the CL script. Functions such as lpar, dpar, dir, and
epar work, but as soon as you try to access a data file, the SPP
program and the script crash.
Does anyone have any ideas of what could be going wrong?
Mike Fitzpatrick wrote on Jan 10, 2006
The default hlib$cl.csh has the line
limit stacksize unlimited
to workaround some memory layout changes in recent kernels. #!cl scripts of course don't use this script so my guess is you need to have that same line defined in the environment that starts the scripts (or "ulimit -s unlimited" for bash shells). Note
that a "!" escape from the script itself won't work, it has to be defined in the parent shell of the CL process.
-Mike
limit stacksize unlimited
to workaround some memory layout changes in recent kernels. #!cl scripts of course don't use this script so my guess is you need to have that same line defined in the environment that starts the scripts (or "ulimit -s unlimited" for bash shells). Note
that a "!" escape from the script itself won't work, it has to be defined in the parent shell of the CL process.
-Mike
Doug Mink wrote on Jan 10, 2006
Mike,
Thanks for the rapid response!!!
"limit stacksize unlimited" does the trick, at least for me in tcsh.
Do you know how to do the same thing in ksh?
-Doug
Thanks for the rapid response!!!
"limit stacksize unlimited" does the trick, at least for me in tcsh.
Do you know how to do the same thing in ksh?
-Doug
Mike Fitzpatrick wrote on Jan 10, 2006
I believe it is the same "ulimit -s" as in bash, don't have a
ksh installed myself.
-Mike
ksh installed myself.
-Mike
Last post on Jan 10, 2006