comment on

I havent used that module, but if you're in *nix, you could use fork without much problem.

As for the InterProcess Communication (IPC) perlipc part, there are a number of options.

I'm partial towards Shared Memory, but it would involve semaphores. From my point of view its the most powerful solution, but consider if your problem merits the extra work (synchronization).

If you need sample code for forking child processes or shared memory, let me know. I must have some stored somewhere.

Heatseeker Cannibal

In reply to Re: Process as daemon, communicate back by HeatSeekerCannibal
in thread Process as daemon, communicate back by owl1

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.


Do you know where your variables are?
	PerlMonks