Alexander V. Lukyanov | 2 Jan 16:21 2006
Picon

Re: lftpget(1) manpage

On Fri, Dec 30, 2005 at 03:48:28PM +0100, Noèl Köthe wrote:
> François Wendling <frwendling free.fr> wrote a small lftpget(1) manpage.
> Maybe you think its better than nothing and likes to add it to your
> releases.

Thanks. I have included it in 3.4.0.

--

-- 
   Alexander.

Alexander V. Lukyanov | 3 Jan 12:57 2006
Picon

Re: lftp

On Tue, Jan 03, 2006 at 10:08:12AM +0100, Kris Van Bruwaene wrote:
> I'm using lftp version  3.3.3 on Debian (Knoppix), and it seems that 
> .netrc is no longer read. Do I need to change the configuration somewhere?

Either use 3.4.0, recently released, or specify user name explicitly and
lftp lftp would use password from netrc.

E.g.:

    lftp user <at> host

--

-- 
   Alexander.

calmar | 3 Jan 23:46 2006

Re: ls error

On Tue, Dec 27, 2005 at 12:19:09PM +0300, Alexander V. Lukyanov wrote:

Hi Alexander,

> > drwxr-xr-x   6 (?)      users         512 Oct 18 16:45 .
> > ls: Fatal error: gnutls_record_recv: A TLS packet with
> > unexpected length was received.
> 
> Please try this patch.
> 

sorry for not replying for such a long time. Additonally I'm
an idiot anyway. I forgot to check it with the latest version. I
used 3.3 while the error above triggered.

Well, with Version 3.4.0, Readline 4.3, Expat 1.95.8, GnuTLS 1.0.16

it workes fine.

So I didn't really check the patch, since I wanted to use the
CVS, but wasn't really able to install that. I guess I would
have to follow the notes ./autogen provides. Should I try that
patch on CVS anyway, even so 3.4 works fine?

sorry again, 
Cheers (g.n.y)
marco

> -- 
>    Alexander.                      | http://www.yars.free.net/~lav/   
(Continue reading)

calmar | 3 Jan 23:48 2006

Re: ls error

On Tue, Dec 27, 2005 at 12:19:09PM +0300, Alexander V. Lukyanov wrote:

hi again,

it seems you already put that patch in on 3.4. Now it works
fine!

Cheers
marco

--

-- 
  calmar

          (o_  It rocks: LINUX + Command-Line-Interface
          //\
          V_/_                     http://www.calmar.ws

Fredrik Arnell | 7 Jan 21:19 2006
Picon

Disable fatal errors?

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

Tobias Geiger | 7 Jan 21:46 2006
X-Face

feature request

Hello!

first: thanks for the greatest cli-ftp client !
ONE little think, and its perfekt (at least for me :)

would it be too complicated, to support wildcards in the "mirror" command?
it's really annoying to do:
"mirror -c bla1 ; mirror -c bla2 ; mirror -c bla3 ; ..." instead of a simple 
"mirror -c bla*" 

Thanks for considering it 

Tobias
Justin Piszcz | 7 Jan 21:42 2006

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?
>
>
(Continue reading)

Fredrik Arnell | 7 Jan 22:13 2006
Picon

SV: Disable fatal errors?

That didn’t 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:
prozzerg <at> dragonfire:~$ ./ftp_check.pl
site: Fatal error: max-retries exceeded
prozzerg <at> dragonfire:~$

/ Fredrik Arnell

-----Ursprungligt meddelande-----
Från: Justin Piszcz [mailto:jpiszcz <at> lucidpixels.com] 
Skickat: den 7 januari 2006 21:42
Till: Fredrik Arnell
Kopia: lftp <at> uniyar.ac.ru
Ä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.
(Continue reading)

Justin Piszcz | 7 Jan 22:21 2006

Re: SV: Disable fatal errors?

From the man page, what is this number set to?  Did you try setting it 
higher?

        net:persist-retries (number)
               ignore  this number of hard errors. Useful to login to buggy ftp
               servers which reply 5xx when there is too many users.

On Sat, 7 Jan 2006, Fredrik Arnell wrote:

> That didn’t 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:
> prozzerg <at> dragonfire:~$ ./ftp_check.pl
> site: Fatal error: max-retries exceeded
> prozzerg <at> dragonfire:~$
>
>
> / Fredrik Arnell
>
>
> -----Ursprungligt meddelande-----
> Från: Justin Piszcz [mailto:jpiszcz <at> lucidpixels.com]
> Skickat: den 7 januari 2006 21:42
> Till: Fredrik Arnell
> Kopia: lftp <at> uniyar.ac.ru
> Ämne: Re: Disable fatal errors?
(Continue reading)

Fredrik Arnell | 7 Jan 23:00 2006
Picon

SV: SV: Disable fatal errors?

Tried setting net:persist-retries to 1, 2, 3 and 10. On 1-3 nothing changed,
but with 10 the script just stalls and nothing happens. 

Current line:
lftp -e "debug off -o /dev/null && set ftp:retry-530 "" && set
net:max-retries 2 && set net:persist-retries 2 && site $cmd && quit" -u
$user,$pass -p $port $host`;

One thing here, both ftp:retry-530 and net:persistas-retries seems to be
settings that are in use when CONNECTED to the server. My problem with the
fatal error is when I tries to connect to a server that is offline.

/ Fredrik

-----Ursprungligt meddelande-----
Från: owner-lftp <at> uniyar.ac.ru [mailto:owner-lftp <at> uniyar.ac.ru] För Justin
Piszcz
Skickat: den 7 januari 2006 22:22
Till: Fredrik Arnell
Kopia: lftp <at> uniyar.ac.ru
Ämne: Re: SV: Disable fatal errors?

From the man page, what is this number set to?  Did you try setting it 
higher?

        net:persist-retries (number)
               ignore  this number of hard errors. Useful to login to buggy
ftp
               servers which reply 5xx when there is too many users.

(Continue reading)


Gmane