Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Fellow Monks:

I'm looking for some general direction on where I can learn more about "process management" (forking, etc.). The best I can gather is that "process management" is just another term for "multitasking" in a UNIX enviornment. I've been reading Chapter 14 of "Learning Perl" and merlyn recommends I "should probably study up on the fork (2) and exec (2) system calls in a traditional UNIX text." But rather than running out and buying a UNIX book, I'd rather find a beginner's guide to process management. Does anyone know of such a beast on the web somewhere? I just want to know some real basic stuff to help me conceptualize it better:

What precisely is process management?
Why would you use it?
What are some common uses for it in Perl?

Thanks for any help you can offer.

$PM = "Perl Monk's";
$MCF = "Most Clueless Friar";
$nysus = $PM . $MCF;


In reply to Process management by nysus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.