iraf.net

I just installed the 64-bit v2.16 system on one of our linux systems. Much seems to work fine, but when I try to put a job in the background (with &, I get the following message:
BKG ERROR: new CL installed; logout and try againI have tried logging out and back in with no luck. Have I made some error in the installation?
Tom

I'll have a closer look tomorrow, but it appears to be an issue that goes back to v2.15 as well and not something you've done. I can reproduce it on a 32-bit system so for the moment you'll need to run in the foreground.

I don't have any problems with v2.15 background jobs.
Tom

This has been fixed and only affects the new VOCL (background jobs were incorrectly using the ECL binary). For 64-bit linux you can get a new binary atftp://iraf.noao.edu/iraf/v216/support/linux64/vocl.eJust download in binary mode and install in your $iraf/bin.linux64 directory. Thanks again for the report.

That has fixed the problem.
Thanks much.
Tom

I am running iraf 2.16 on an iMac running Mac OS X 10.9.5 and am having the same error:

BKG ERROR: new CL installed; logout and try again

I tried the solution of downloading the file mentioned above but, perhaps not surprisingly, I was unable to execute the command due to architecture mismatch.

Any ideas how to get this fixed these days?

The proper binary for your system is available at

ftp://iraf.noao.edu/iraf/v216/support/macintel/vocl.e

Download in binary mode, make executable and put in your $iraf/bin.macintel directory.

I realize it's been quite a while since the solution was posted, but I've just now had the chance to try it out. Sorry to say that this did not fix the problem. I still get this error:

vocl\$this->_split2($m[0]) BKG ERROR: new CL installed; logout and try again

Any further suggestions are more than welcome!

I can confirm now that this problem is either unrelated to Mac OS X 10.9.5 or at least also present with 10.7.5. Both Macs that I ran into this problem with are running V2.16 though. (And both are 64-bit.)

That seems a bug in the 2.16/2.16.1 code; I just filed a bug report #131 on github.