host cl scripting capability
Tom Duvall wrote on Nov 01, 2007
I was trying to make use of the "host cl scripting capability" as described in the document by the same name. I couldn't make my own stuff work so I tried one of the examples in the document and could not get it to work. The example (with slight modifications for where we have iraf):
#!/usr/local/iraf/iraf/bin.redhat/cl.e -f
set imdir="HDR$pixels/"
logver ="IRAF V2.11 May 1997"
set arch=.redhat
images
imutil
printf ("imarith %s\n", args) | cl()
logout
When I execute this with the following command line:
./test dev\$pix \* 10 newimg.fits
I get the following response:
PANIC in `/usr/local/iraf/iraf/bin.redhat/x_images.e': Memory has been corrupted
and it goes into an infinite loop.
My system is a linux one x86_64. Iraf works fine in general but I need to supply some software to others that needs to be executed from the host.
Thanks.
Tom Duvall
#!/usr/local/iraf/iraf/bin.redhat/cl.e -f
set imdir="HDR$pixels/"
logver ="IRAF V2.11 May 1997"
set arch=.redhat
images
imutil
printf ("imarith %s\n", args) | cl()
logout
When I execute this with the following command line:
./test dev\$pix \* 10 newimg.fits
I get the following response:
PANIC in `/usr/local/iraf/iraf/bin.redhat/x_images.e': Memory has been corrupted
and it goes into an infinite loop.
My system is a linux one x86_64. Iraf works fine in general but I need to supply some software to others that needs to be executed from the host.
Thanks.
Tom Duvall
Mike Fitzpatrick wrote on Nov 01, 2007
Try adding the command
limit stacksize unlimited
to your .cshrc environment (or "ulimit -s unlimited" to your Bash environment if you use that). This works around some memory changes in recent v2.6 kernels and is done automatically in the CL startup script, but with #!cl scripts it needs to be part of your linux environment.
Cheers,
-Mike
limit stacksize unlimited
to your .cshrc environment (or "ulimit -s unlimited" to your Bash environment if you use that). This works around some memory changes in recent v2.6 kernels and is done automatically in the CL startup script, but with #!cl scripts it needs to be part of your linux environment.
Cheers,
-Mike
Tom Duvall wrote on Nov 01, 2007
Great!
Last post on Nov 01, 2007