in reply to simple IPC needed

You probably want the daemon to listen on some port with IO::Socket::UNIX or IO::Socket::INET. If you want to get modern, have POE do the heavy lifting. Its cookbook has examples which would probably take little work to adapt to your requirements.

You can't really have a daemon watch for keyboard activity. A daemon has no controlling terminal, so whose keystrokes should it watch? The point of a daemon is that whoever wants to use it should connect in a known way. It's up to the client to produce the socket message on an event. That way the daemon doesn't need to know anything about the client.

After Compline,
Zaxo

Replies are listed 'Best First'.
Re^2: simple IPC needed
by redss (Monk) on Feb 18, 2005 at 13:19 UTC
    thanks for your reply, but I messed up on my terminology, I shouldn't have stated the one process would be a daemon, I actually meant that although it would constantly run, it would take a tty session, not run in the background (as opposed to the other which would briefly run then stop.

    I was thinking of using signals such as in perlipc, but I couldn't find any simple examples in the perlipc doc.