Thanks for the reply. Reading the csh man page I got to the same conclusion. Not having any need to have a .profile loaded or a .cshrc executed for my job I overcame the problem using -f as a switch to csh, thereby avoiding to fix something I'm not interested into. Shell starts good now, while shell scripts (putting -f switch on the shebang) start and get executed good as well but with the same error message printed on stderr.
Anyway...
Leave a comment: