In this case, you're doing some things which are actually pretty simple shell stuff. While [id://shmem] is correct that it can get tedious translating Perl to shell, his suggestion for creating a Perl shell seems a little like overkill here.

You should be able to get this to work as you intended by simply connecting to the remote host, then executing 

@filecont = $telnet->cmd("grep -i '$contcheck' $directory/$checkfile")
+;
if (@filecont) {
  $status = 'FAIL';
} else {
  $status ='PASS';
}

[download]
No directory handles or evaluating each line of the file necessary, just ask the remote host to run the grep for you and react based on whether it found any matches or not.

In reply to Re: Remote server file access issue by dsheroh
in thread Remote server file access issue by qsl

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.