Actually none of the problems that I had have anything to do with my command line client and were all either ftp or sftp or lftp connected. The solution I found works though I later learned about putting macros in my .netrc file to handle updates like this. I will find out if those macros work later today. These macros will not be machine-specific since I have other things I do with those machines as well. If those machines were special-purpose machines dedicated to file updates I'd need to write those macros in another way. I'm holding on to the scripts I wrote in case the .netrc solution proves to be a failure too. On Wed, 18 Jun 2014, Sam Hartman wrote: > None of what you're talking about sounds like a comment on the ftp or > sftp protocol. > It sounds like concerns about the particular command-line client you're > using. > > I think if you write something in perl, python or ruby and use a library > for sftp or ftp you'll find that these sort of issues don't come up. > > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/blinux-list > > jude <jdashiel@xxxxxxxxxxxxxx> _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list