Re: Getting STDOUT from daemon a to a socket on daemon b

On 2007-07-07, Rainer Weikusat <rweikusat@xxxxxxxxxxx> wrote:
Grant Edwards <grante@xxxxxxxx> writes:
On 2007-07-07, Rainer Weikusat <rweikusat@xxxxxxxxxxx> wrote:
Grant Edwards <grante@xxxxxxxx> writes:
On 2007-07-07, mike@xxxxxxxxxxxxxxx <mike@xxxxxxxxxxxxxxx> wrote:

Can anyone tell me the correct way to bridge the gap between these two
programs that will consume the least resources?

http://netcat.sourceforge.net/

Netcat does not support PF_UNIX sockets (socat would be a
better choice for that). But both come with half a million of
features not needed for simple forwarding (eg netcat has a
built-in port scanner), which slow them down to some degree.
If the OP is as performance constrained as he claims to be, a
more specialized approach makes more sense.

Sure, if the computer's time is more valuable than the user's
time. :)

My time is the resource I value more.

That doesn't make netcat any more capable of dealing with unix domain
sockets

The OP stated that an IP socket was acceptible: (e.g.
127.0.0.1:10024).

and the people waiting for their e-mail are the actual users
whose time is of value here.

True, but I'd still try an existing program before jumping to
the conclusion that it's too slow and therefore should be
replaced by a custom application.

--
Grant Edwards grante Yow! I'm having BEAUTIFUL
at THOUGHTS about the INSIPID
visi.com WIVES of smug and wealthy
CORPORATE LAWYERS ...
.

Relevant Pages