Cron job sometimes has a different profile from the normal login session. So check your environment, see if they are the same. This should have little to do with ssh itself. --Steve
Benoit Langevin <[EMAIL PROTECTED]> on 10/03/2001 06:15:30 PM To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: (bcc: Horng-Twu Lihn/Telcordia) Subject: Crontab problem On the SCO system we have here, we which to you a cron job that will go and grab the data from machine a and use it on machine b. The problem is that the script works when call on by a user in a shell, but not on the cron. To complicate our research of the problem, it works fine at the command prompt and as a cron job on a Sun Solaris system. I have tested with openssh 2.9p2 and upgraded to 2.9.9p2, and the problem is the same on both. Hope someone can help. Here is the script that is run in the cron job <<<<< $ cat test.scp #!/bin/ksh #set 2>&1 > /tmp/set.out TERM=vt100;export TERM PATH=$PATH:/usr/local/ssh/bin ssh -q -o "BatchMode yes" <destination_server> 'env' > /home/langevin/test.out >>>>> This is the output that cron send in an e-mail Important line is select: Invalid argument <<<<< OpenSSH_2.9.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090601f select: Invalid argument >>>>> Thanks Benoit Benoit Langevin, B. Sc. Analyst-Programmer SunGard EMS - Brokerware(tm) Tel: (514) 982-6687 x 231 Fax: (514) 982-9476 e-mail: [EMAIL PROTECTED] web: www.sungardems.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
