On 6 May 1998, Manoj Srivastava wrote:
> __> ~/src/ftp-get ftp://ftp.debian.org/debian/README README > F ftp://ftp.debian.org/debian/README > I Connecting to ftp.debian.org > I setting type to binary > I getting modified time for /debian/README > I getting /debian/README > I resetting modified time for README > I Closing connection > I Trying to get md5sum for README > M 99e7acd0783cfb1b29de5d09c761241a > __> ~/src/ftp-get ftp://ftp.debian.org/debian/README README > F ftp://ftp.debian.org/debian/README > I Connecting to ftp.debian.org > I setting type to binary > I getting modified time for /debian/README > I Local file README exists > I local modified time matches > I getting size for /debian/README > I Already have README with size 1057 This is a bit more verbose than I intended methods to be, but that shouldn't be a problem. But there are a few glitches in this output, the first run must printout the file size using the S tag. Also, the line 'getting /debian/README' should be changed to be 'Downloading' (this will cause the I line to not be shown). Similarly, if you are resuming a file then print out 'Resuming (size)' Also, it's best if long term I lines are short so they don't take up much space on the single line display. Right now I'm thinking of making an L keyword that would log things into the log file if some debug flag was set, I wasn't really ment for all of what you are sending out. (things that take a small constant time should not be I lines) Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
