Modified two lines, see comment:

sub authUser
{
    # open two-way pipe to auth script (or die with an error)
    my($h,$in,$out,$err,$t);

    my @cmd = ( $pathToPerl, './auth.pl' );

    eval
    {
        $h = harness(\@cmd, \$in, \$out, \$err, $t=timeout (5)); #modi
+fied this line to fix timeout syntax
        start($h);
        $in = "$cUser\n$cPass\n";

        pump($h) while length($in);  ## Wait for all input to go
        pump($h) until $out =~ m/\n\x1E\x1E\x1D\x1E/;

        finish $h;
    }; #modified this line, added ';'

    if ($@) {
        $h->kill_kill;
        die("failed to connect to authorization module: $@");
   }
}

[download]

In reply to Re: identifying an IPC::Run + eval block error by pg
in thread identifying an IPC::Run + eval block error by EvanK

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.