I know this does not help your actual error, but in the interest of security, there are a few things ...

I would suggest doing a few things. For each of the m//i's in the if/else, i suggest using lc(), and then using eq ... this prevents evil hacker code man motd from matching m/motd/i. Also, on the non-trusted user front, having the command coded in is very good, but i would think that the environment could have some very usefull information in it, were the wrong person to be pokiing around. This best thing to do, in the short term, is design a protocal for logging in (something as simple as FTP's login procedure).
Lastlky, on the error, i do not believe programs like motd use \r\n for newlines, so it is possible that is causing some issues. 
$ perl -e 'do() || ! do() ;'
Undefined subroutine &main::try

[download]

In reply to Re: A Perl Server Daemon by MZSanford
in thread A Perl Server Daemon by emcb

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.