That didnt help, still getting those errors I'm afraid. It maybe helps a bit to see the command I use: lftp -e "debug off -o /dev/null && set ftp:retry-530 "" && set net:max-retries 2 && site $cmd && quit" -u $user,$pass -p $port $host
and when I run it I get this: [EMAIL PROTECTED]:~$ ./ftp_check.pl site: Fatal error: max-retries exceeded [EMAIL PROTECTED]:~$ / Fredrik Arnell -----Ursprungligt meddelande----- Från: Justin Piszcz [mailto:[EMAIL PROTECTED] Skickat: den 7 januari 2006 21:42 Till: Fredrik Arnell Kopia: [email protected] Ämne: Re: Disable fatal errors? If you type set -a it will show you all of the things you can set. set ftp:retry-530 "too many|overloaded|try (again |back )?later|is restricted to|maximum number|number of connect|only.*session.*allowed|more connection" I believe this defines the regexes that determine whether the error is fatal or not, perhaps setting it to "" may fix your problem? Justin. On Sat, 7 Jan 2006, Fredrik Arnell wrote: > Hi everyone. Im currently developing a perl script to connect and send a > command to an ftp server and return the answer. > Everything works, BUT if the remote server doesn't allow me to connect I get > this error msg: > site: Fatal error: max-retries exceeded > > Is there any switch or parameter to NOT send this kind of errors? Because > that sort of error messages makes crond to send a mail to the user I run my > script as, because it detects as an "error". If I run the script "by hand" I > get those errors too, but the script continues to run until its done. > > I tried with "debug off -o /dev/null", no luck there. > > So is it possible to turn off this sort of errors without editing out the > event rising code about errors from the source code? > > > > / Fredrik Arnell > >
