There's no reason to fork in this situation when this is something that can be done easily using the SMTP protocol. Forking introduces a WHOLE mess of unnecessary problems into a simple script that could potentially kill the server ie, infinite loops. Also, forking without knowing how to clean up your children is a bad idea. AND in the event the forking loop spins off into infinity and a successful connection is made to a mail server, think of the load that'll put on the mail server unnecessarily (it could potentially use up all available file descriptors and render the mail server unreachable until the connections close).
bottom line, that is WAY too complicated, but if you're still interested I wrote up a
node on forking that might be useful. I took time to read several different books and various web pages online for possible problems that I could encounter.
K.I.S.S.
-brad..
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.