Beefy Boxes and Bandwidth Generously Provided by pair Networks RobOMonk
Think about Loose Coupling
 
PerlMonks  

Re: Sending commands to another process that isn't expecting it

by mellon85 (Monk)
on Dec 05, 2010 at 09:43 UTC ( #875473=note: print w/ replies, xml ) Need Help??


in reply to Sending commands to another process that isn't expecting it

As you are forking the process you can keep track of the PID of the children and use signals to tell the child to wait for a message in the pipe using the function kill


Comment on Re: Sending commands to another process that isn't expecting it
Re^2: Sending commands to another process that isn't expecting it
by Anonymous Monk on Dec 05, 2010 at 11:25 UTC

    The process issuing the commands to the daemon will not be a parent of the daemon.

    Should I just send a SIGUSR1 to the daemon process using kill and then in the handler for SIGUSR1 in the daemon have it check a fifo file for input?

      That's exactly what I meant

        There isn't such a thing as a bidirectional FIFO is there? I tried opening both FIFOs as "+<" but it didn't work as expected. I suppose if I want the daemon to communicate back and send an "OK" message or anything I'd have to switch up the read/write mode on both ends?

Re^2: Sending commands to another process that isn't expecting it
by mikealeonetti (Novice) on Dec 05, 2010 at 11:37 UTC
    That uh... Anonymous response was actually from me. I didn't see that I wasn't logged in... Embarrassingly enough.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://875473]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (5)
As of 2014-04-19 16:44 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (483 votes), past polls