comment on

Daemonizing your scripts doesn't really have anything to do with inter process communication. I know some folks use network sockets for communication between perl programs and there's some discussion over in the Q&A section under network programming section and a little bit under the programs and processes section. You could also search around the IPC modules on CPAN.

Hope that helps. I'm not experienced in these matters personally, just some observations.

--
naChoZ

Therapy is expensive. Popping bubble wrap is cheap. You choose.

In reply to Re: Process as daemon, communicate back by naChoZ
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.


Perl Monk, Perl Meditation
	PerlMonks