Greetings fellow avout,

I'm working on an IRC bot. Currently the bot listens for messages on the channel. I want add a feature that will read an external feed (e.g. github api) and send messages to the channel based on the return. My thought was to fork a separate process for that. This is a forking POC prototype. Am I on the right track and what kind of fork safety features should I include? 

#!/usr/bin/perl

use strict;
use warnings;
use feature 'say';

if ( fork )
{
   while ( 1 )
   {
      say "Listening for irc public message";
      my $msg = <STDIN>;
      chomp $msg;
      say "Your message: $msg";
   }
}
else
{
   while ( 1 )
   {
      sleep 15;
      say 'Walking up to read a feed and send a message';
   }
}

[download]

Neil Watson
watson-wilson.ca

In reply to Safe forking by neilwatson

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.