|
Hmmm - it looks like the file you are GETting is growing. Are you able to get on the remote system and see its contents? The '150' message comes from the server. It seems to say there are that many bytes in the object on that server. The count is almost as many as are transferred. GET has never has an APPEND feature, that I know of. You could CLRPFM in whatever runs ftp, right? Or put a '!' in the script with a 'clrpfm' after it. The '!' means to run the local command that follows it. It's a synonym for 'syscmd' At 11:24 AM 4/8/02 -0400, you wrote: >-- >-- >[ Picked text/plain from multipart/alternative ] >I am actually seeing more records. The file grows in size with each FTP. I >want to clear the damn file with every session, or delete it, or something. >I don't really care what works, but something has to work. > > >-------------------------------------------- >Booth Martin >MartinB@Goddard.edu >802-454-8315 x235 >-------------------------------------------- >-------Original Message------- > >From: midrange-l@midrange.com >Date: Monday, April 08, 2002 12:17:15 PM >To: midrange-l@midrange.com >Subject: Re: FTP (replace Not working as expected > >Are you actually seeing more records? Or is this based on the byte counts >you see? There are conversion issues, EOR characters, etc., that can make a >count appear larger than the result has. > >At 11:06 AM 4/8/02 -0400, you wrote: > >Here's the log of an FTP session: > > > >"> get lastTransfer.txt WEBINQ1 (REPLACE > >227 Entering Passive Mode (216,114,155,110,11,198) > >150 Opening connection (1244222 bytes) > >226 Transfer complete > >1246003 bytes transferred in 56.050 seconds. Transfer rate 22.230 > > KB/sec." > > > >I am expecting this command to replace the data in the physical file >WEBINQ1 > >but it appears to be appending records. Any idea what I am missing? > > > > > >-------------------------------------------- > >Booth Martin > >MartinB@Goddard.edu > >802-454-8315 x235 > >-------------------------------------------- > >_______________________________________________ > >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > >To post a message email: MIDRANGE-L@midrange.com > >To subscribe, unsubscribe, or change list options, > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > >or email: MIDRANGE-L-request@midrange.com > >Before posting, please take a moment to review the archives > >at http://archive.midrange.com/midrange-l. > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. > > >. >-- >[ Content of type unknown/unknown deleted ] >-- > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.