Alexander,

I think it's the "newer than" member that needs to be
adjusted to solve my 
issue.
However, I think the same might also be true with
"older than" as well 
(which
you changed) but I do not use that currently.
Basically, it's how to handle 
timestamps
that match the arg to the second. Currently, they get 
included but I don't 
think they
should (matching what the doc states)...but, that is,
of course, open to 
debate.

What I did to get around this issue for the time being
was add the touch 
command

touch -r $Lastfile -F 1 lastfile

to my lftp driver script which takes the last file
transferred
down from the ftp site and creates the "lastfile"
sentinel 1 (one)
second in the future so that the last file does not
get included
again in the next pull.

Thanks for looking at this,

Michael

----- Original Message ----- 
From: "Alexander V. Lukyanov" <[EMAIL PROTECTED]>
To: "Michael Leib" <[EMAIL PROTECTED]>
Cc: <[email protected]>; "John Thompson"
<[EMAIL PROTECTED]>; 
"Peter Sites" <[EMAIL PROTECTED]>
Sent: Sunday, August 05, 2007 9:48 PM
Subject: Re: Possible Bug in lftp


> On Fri, Aug 03, 2007 at 04:53:51PM -0700, Michael
Leib wrote:
>> But, it appears it's doing "equal to and newer than
a specified time".
>
> Does the attached patch help?
>
> -- 
>   Alexander.                      | software is
knowlege
> 




       
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, 
photos & more. 
http://mobile.yahoo.com/go?refer=1GNXIC

Reply via email to