in reply to redirection of output

Well, if you have two different machines, you have to have a wire protocol to get the data across. It doesn't just magically leap from one place to another.

The simplest would be to run process X as a CGI program, then machine B can simply request that machine A run process X and the output sent in response.

If that doesn't meet your needs, you'll have to be more specific.

-- Randal L. Schwartz, Perl hacker

Replies are listed 'Best First'.
RE: Re: redirection of output
by djw (Vicar) on Sep 14, 2000 at 19:46 UTC
    What I am looking to do is this:

    Machine A = perl program runs a dedicated quake server and pumps output of console to Machine B using a Perlbot in irc
    Machine B = runs a perlbot in irc that can pump out console info and accept and send quake server commands to Machine A.

    Basically a client/server admin tool using IRC.

    Links:
    Perlbot Perlbot Quake3Plugin Similar GUI based (Tcl/Tk) program used for Half-Life servers

    Not the noblest of causes but its a fun project. =)

    Thanks, <a href="http://www.perlmonks.org/index.pl?node_id=16711&lastnode_id=2437"djw
      So, you can still use HTTP, but it's probably overkill unless you want some sort of security.

      Short of that, one solution is to set up a TCP server socket on the quake machine, and have it broadcast whatever's showing up to any and all clients that connect. Then write a simple TCP client on the perlbot side, and when data is ready, feed it to the perlbot.

      -- Randal L. Schwartz, Perl hacker