CL dies on new 64bit OSX 10.6.7 installation

[mcintoshdh]

Hello,

I successfully installed v2.15.1a on my new MacBookPro running 64bit
uname -m ==> x86_64
using iraf.macx.x86_64.tar.gz; installation was smooth (from iraf admin user)

but after doing a clean mkiraf (from my user account) when I start cl I get:

ERROR: Cannot change directory to `danmcintosh'
called as: `chdir (danmcintosh)'
called as: `cl ()'
called as: `cl ()'
Error while reading login.cl file - may need to rebuild with mkiraf
Fatal startup error. CL dies.

I don't understand, as all danmcintosh directories in login.cl are good:

set home = "/Users/danmcintosh/"
set imdir = "/iraf/imdirs/danmcintosh/"
set uparm = "home$uparm/"
set userid = "danmcintosh"

What did I do wrong??
Thanks

[fitz]

The chdir() is being done in the hlib$extpkg.cl script that dynamically loads the external packages. Because this script is executed before the normal system commands are available to the CL, it uses host commands (e.g. '!pwd' instead of "path") for certain operations. Is it possible your use directory contains a space in the name (e.g. "/Users/dan mcintosh")? If not, the are you logging in from /Users/danmcintosh or some other directory? If you do a MKIRAF in the /tmp directory and type 'cl' from there, do things work (indicating a problem in your iraf login directory and not the iraf installation directory).

[mcintoshdh]

Hi,

I login to /Users/danmcintosh, which is where I ran mkiraf.
I installed iraf as an admin user = iraf. I installed external packages from the same. When I ran cl from /Users/iraf it worked fine.

I have sudo privileges, is it still necessary to install iraf from an iraf user account?

Thanks

[fitz]

Strictly speaking, it was never actually necessary to create an iraf user account (it was a convenience to have an environment defined with things an iraf site-admin would need), although the install script still needs to be run as root (for now, that will change for the next release) the iraf tree itself can be owned by anyone.

That said, be sure the /Users/iraf directory has read permissions for other users. You can put the command 'd_trace' at the top of the hlib$extpkg.cl script to have it print what it's actually doing, that might offer some sort of clue.

[mcintoshdh]

Problem solved, thanks for the tip.

Very weird problem discovered by adding d_trace to top of hlib$extpkg.cl -- I have an old .alias file with the following defunct command to end a ssh connection:
alias end 'ps aux |grep nova1'
This was the culprit, who knows why .. who cares. Iraf works now!

Note for those interested, even though I set up iraf admin user, everything was loaded using sudo in the correct /iraf/iraf/ directory structure.