Interesting! Here's what I got.. - had trouble running it with -wT in line 1; was able to run it after cutting that out as you suggest, perl -wT perlsvr.pl perlsvrhome
- could not get -h to work (I think this and above mean my getopts or something is corrupt)

- does not close connection right away though kills child.
- sending ctrl-c instead of something like GET / causes child to quit with "Use of uninitialized value at /usr/lib/perl5/site_perl/5.005/HTTP/Daemon.pm line 498." which is a funny reason to quit..
- was able to download a file set to chmod 700 and ending in .pl

So I'm not so sure about the security side, although presumably perl's proof against buffer attacks, we are told. How about keeping a list of children and killing them after a certain amount of time just in case? I wanted to do a kill -HUP on it when I had made a lot of children processes, but it just died.

The

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.