comment on

As has already been hinted at, it isn't necessary to spawn and reap threads during operation, only at startup and shutdown of the service as a whole.

IPC::Semaphore and IPC::SysV (IPC = interprocess communication) contain all the technology you'll need for a master process to communicate with its living children (semaphores, which are part of the operating system, are the most efficient way to manage locking and triggering with shared memory).

See also the System V IPC Chapter of Programming Perl by Larry Wall, Tom Christiansen, and Jon Orwant ISBN 0-596-00027-8 for a nice code example of how to use fork with shared memory and semaphores so that the processes can stay alive and remain in contact for control purposes.

One world, one people

In reply to Re: Reliable asynchronous processing by anonymized user 468275
in thread Reliable asynchronous processing by Codon

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.


P is for Practical
	PerlMonks