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

[mellon85]

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

[Anonymous Monk]

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?

[mellon85]

That's exactly what I meant

[mikealeonetti]

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?

[mikealeonetti]

That uh... Anonymous response was actually from me. I didn't see that I wasn't logged in... Embarrassingly enough.