HP3000-L Archives

May 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Thu, 13 May 1999 10:20:10 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
Rick Clark wrote:
>
> I received the following error when we ftp'd certain files to a HP9000
> and cannot find any clues as to what this means. I did a search on the
> ESC and found two documents. One was blank, and the other was no help.
> Has anyone seen this error before?

>  File Transfer Protocol [A0008S33] (C) Hewlett-Packard Co. 1990
>  ftp> put ACT999
>  200 PORT command successful.
>  150 Opening ASCII mode data connection for ACT999.
>  226-WARNING! 1918 bare linefeeds received in ASCII mode
>     File may not have transferred correctly.
>  226 Transfer complete.
>  40140100 bytes sent in 74.17 seconds (528.48 Kbytes/sec)

ASCII text is transferred by FTP over the wire with records delimited
by <cr><lf> sequences.  This "is" ASCII text to DOS, for example; for
Unix the <cr> must be removed; for MPE they are both removed (for a
flat text file).  But the point remains that "in transit" they have
the <cr><lf> sequence, and neither <cr> nor <lf> should appear in
the "ASCII text" payload of the record.

A "bare linefeed" occurs when a <lf> is detected without a preceding
<cr>, and suggests that you are really transferring binary data as
opposed to ASCII text, or at a minimum you have some stray control
characters in your text.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2