<?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: Perl vs shell scripts for FTP in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246074#M891556</link>
    <description>I had made a similier request and I found ,&lt;BR /&gt;&lt;BR /&gt;1. It can give you a return code which shell script can not give you for a proper and improper file transfer.&lt;BR /&gt;&lt;BR /&gt;Regds,&lt;BR /&gt;&lt;BR /&gt;Kaps</description>
    <pubDate>Tue, 13 Apr 2004 02:10:57 GMT</pubDate>
    <dc:creator>KapilRaj</dc:creator>
    <dc:date>2004-04-13T02:10:57Z</dc:date>
    <item>
      <title>Perl vs shell scripts for FTP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246073#M891555</link>
      <description>Hi there,&lt;BR /&gt;&lt;BR /&gt;I've noticed several threads discussing the automation of FTP using Perl and shell scripts and was wondering about the pro's and con's of either approach. &lt;BR /&gt;&lt;BR /&gt;For example, how's the performance of Net::FTP compared to standard FTP? &lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Ben</description>
      <pubDate>Tue, 13 Apr 2004 02:05:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246073#M891555</guid>
      <dc:creator>Benjamin Cheong</dc:creator>
      <dc:date>2004-04-13T02:05:01Z</dc:date>
    </item>
    <item>
      <title>Re: Perl vs shell scripts for FTP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246074#M891556</link>
      <description>I had made a similier request and I found ,&lt;BR /&gt;&lt;BR /&gt;1. It can give you a return code which shell script can not give you for a proper and improper file transfer.&lt;BR /&gt;&lt;BR /&gt;Regds,&lt;BR /&gt;&lt;BR /&gt;Kaps</description>
      <pubDate>Tue, 13 Apr 2004 02:10:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246074#M891556</guid>
      <dc:creator>KapilRaj</dc:creator>
      <dc:date>2004-04-13T02:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: Perl vs shell scripts for FTP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246075#M891557</link>
      <description>I fully agree with Kapil, that that is the most important switch to choose for.&lt;BR /&gt;&lt;BR /&gt;On avarage, the speed is not depending on the scripting language, but on the speed of your  connection line.&lt;BR /&gt;&lt;BR /&gt;Several smaal commands might be faster in shell, whereas a few large transfers are easier dealt with in Perl.&lt;BR /&gt;&lt;BR /&gt;Due to the fact that errors are easier cought in Perl, retransfers are a breathe in perl, where it is a pita in sh scripts.&lt;BR /&gt;&lt;BR /&gt;Enjoy, Have FUN! H.Merijn</description>
      <pubDate>Tue, 13 Apr 2004 02:33:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246075#M891557</guid>
      <dc:creator>H.Merijn Brand (procura</dc:creator>
      <dc:date>2004-04-13T02:33:05Z</dc:date>
    </item>
    <item>
      <title>Re: Perl vs shell scripts for FTP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246076#M891558</link>
      <description>Ben,&lt;BR /&gt;&lt;BR /&gt;One of the other major benefits is that if you have a Windoz server set up properly, you can use the NetFTP module to automate ftp from windows to another platform, shell scripts aren't generally avaliable for windows OS. ( I know about the various Unix shell products... they dont count in this reply).&lt;BR /&gt;&lt;BR /&gt;Scott</description>
      <pubDate>Tue, 13 Apr 2004 15:16:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246076#M891558</guid>
      <dc:creator>Scott Palmer_1</dc:creator>
      <dc:date>2004-04-13T15:16:14Z</dc:date>
    </item>
    <item>
      <title>Re: Perl vs shell scripts for FTP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246077#M891559</link>
      <description>If you want something that is at best ugly, do it in Shell but make sure that you put FTP in verbose mode. Perl's NET::FTP instantly and easily gives you error checking and nice, clean code. The transfer performance will be indistinguishable.&lt;BR /&gt;&lt;BR /&gt;The attached ftpput.pl should give a good starting point. Invoke as ftpput.pl -u for full usage.</description>
      <pubDate>Tue, 13 Apr 2004 15:33:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246077#M891559</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-04-13T15:33:02Z</dc:date>
    </item>
    <item>
      <title>Re: Perl vs shell scripts for FTP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246078#M891560</link>
      <description>If you want something that is at best ugly, do it in Shell but make sure that you put FTP in verbose mode. Perl's NET::FTP instantly and easily gives you error checking and nice, clean code. The transfer performance will be indistinguishable.&lt;BR /&gt;&lt;BR /&gt;The attached ftpput.pl should give a good starting point. Invoke as ftpput.pl -u for full usage.</description>
      <pubDate>Tue, 13 Apr 2004 15:33:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/perl-vs-shell-scripts-for-ftp/m-p/3246078#M891560</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-04-13T15:33:03Z</dc:date>
    </item>
  </channel>
</rss>

