Re: Process as daemon, communicate back

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

Comment on Re: Process as daemon, communicate back

Replies are listed 'Best First'.
Re^2: Process as daemon, communicate back by owl1 (Initiate) on Dec 24, 2007 at 04:03 UTC
Thanks Cannibal Sample code involving independent process accessing the same data with the use of "IPC::Shareable" would be helpful Also, the processes are all on the same machine Thanks	[reply]