I have a piece of code
#! /usr/local/bin/perl use Oraperl; use DBI; use FileHandle; use rf; use IO::Socket; use IO::Handle;; use POSIX qw(setsid); die "syntax: $0 port" if 1 > @ARGV; $port=$ARGV[0]; open STDIN, '>/dev/null' or die "Can't read /dev/null: $!"; print "Step 1\n"; open STDOUT, '>','/dev/null' or die "Can't write to $prout: $!"; print "Step 2\n"; open STDERR, '>/dev/null' or die "Can't write to $prerr: $!"; ...
This piece of code works fine on HP-UX with version:# perl -v This is perl, v5.8.3 built for IA64.ARCHREV_0-thread-multi-LP64 But now that we are migrating to Linux (RedHat 6.6), the code fails on the command: open STDOUT, '>','/dev/null' or die "Can't write to $prout: $!"; putting this line into comment, then it works. Perl version on LINUX: perl -v This is perl, v5.10.1 (*) built for x86_64-linux-thread-multi Any ideas what is causing this?

In reply to Perl migration hp-ux -> Linux by vccs

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.