<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ftp in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679108#M589495</link>
    <description>Probably not.  My FTP process just gives up if it has problems.  After a successful FTP it moves the file to the Archive directory so I have a script which checks periodically to see if the To_Send folder has any files and if it finds one restarts the FTP send process. If it doesn't go this time it will usually go the next time.&lt;BR /&gt;&lt;BR /&gt;Ron</description>
    <pubDate>Fri, 08 Mar 2002 18:43:54 GMT</pubDate>
    <dc:creator>Ron Kinner</dc:creator>
    <dc:date>2002-03-08T18:43:54Z</dc:date>
    <item>
      <title>ftp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679107#M589494</link>
      <description>I have a process that ftp's multiple large files from my local HP box to another.  At times one of the files does not transfer fully and I get "sendfile: Broken pipe" message in root mail.  My question is: Is ftp smart enough to recognize this condition and resend that file?  Right now, I manually check for this and resend the file.  I'm looking for any information or suggestions on how to automate this.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for all responses.&lt;BR /&gt;&lt;BR /&gt;Nancy</description>
      <pubDate>Fri, 08 Mar 2002 18:37:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679107#M589494</guid>
      <dc:creator>Nancy Bahouth Spirakis</dc:creator>
      <dc:date>2002-03-08T18:37:56Z</dc:date>
    </item>
    <item>
      <title>Re: ftp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679108#M589495</link>
      <description>Probably not.  My FTP process just gives up if it has problems.  After a successful FTP it moves the file to the Archive directory so I have a script which checks periodically to see if the To_Send folder has any files and if it finds one restarts the FTP send process. If it doesn't go this time it will usually go the next time.&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Fri, 08 Mar 2002 18:43:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679108#M589495</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2002-03-08T18:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: ftp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679109#M589496</link>
      <description>No, unfortunately FTP isn't that smart.  What you could have a look at though is the NET::FTP module for Perl.  I don't have any experience with this personally, but have heard about what it can do from A. Clay Stephenson.  I'm sure he can tell you more about it.</description>
      <pubDate>Fri, 08 Mar 2002 18:44:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679109#M589496</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2002-03-08T18:44:23Z</dc:date>
    </item>
    <item>
      <title>Re: ftp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679110#M589497</link>
      <description>What I have done in the past is one of two things.&lt;BR /&gt;&lt;BR /&gt;1. Use rcp when ever possible. This may not be possible for you.&lt;BR /&gt;&lt;BR /&gt;2. When I must use ftp I script the ftp put then when the put command completes, I use ftp to create a file that list the files in the directory on the target server. I then break out of ftp and check for the file name that I sent in the ftp command. If the file isn't on the target system I either report an error or retry the ftp put.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Mar 2002 19:43:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679110#M589497</guid>
      <dc:creator>Krishna Prasad</dc:creator>
      <dc:date>2002-03-08T19:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: ftp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679111#M589498</link>
      <description>Hi Nancy:&lt;BR /&gt;&lt;BR /&gt;Since that pesky Patrick gave me some homework to do, here is a Perl script that will do what you want.&lt;BR /&gt;&lt;BR /&gt;It first logs you in to a remote server, change the remote host, user, and password to suit your needs. It then does a cwd to /tmp and puts ftp in 'binary mode'. It then reads the command line for filenames to send. It will try each one up to 5 times. The beauty of doing this in perl is that the error checking is built right in. You will need to download and install the Net::FTP module from &lt;A href="http://www.perl.org/CPAN" target="_blank"&gt;http://www.perl.org/CPAN&lt;/A&gt; but after that you are done. I never bother trying to do this stuff in the shell anymore because this is so much easier.&lt;BR /&gt;&lt;BR /&gt;P.S. If you need to punch through a proxy server, simply supply a 3rd argument to the login subroutine and it will be just like you typed the account ftp command yourself.&lt;BR /&gt;&lt;BR /&gt;Regards, Clay</description>
      <pubDate>Fri, 08 Mar 2002 20:52:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp/m-p/2679111#M589498</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-03-08T20:52:22Z</dc:date>
    </item>
  </channel>
</rss>

