Re: Process control from LAN master computer
From: Drieux (drieux_at_wetware.com)
Date: 03/29/04
- Next message: Wc -Sx- Jones: "Re: warn ?!"
- Previous message: Paul Johnson: "Re: warn ?!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 28 Mar 2004 15:26:03 -0800 To: Perl Beginners Mailing List <beginners@perl.org>
On Mar 24, 2004, at 8:43 AM, Peterson, Darren - Contractor.Westar wrote:
[..]
> I tried Proc::Background so my script wouldn't wait on the invoked
> task as
> with the Perl system command. Actually, I've found that ssh isn't
> what I
> need since the invoked task displays on the local, and not remote,
> machine.
are you 'getting off' to the far host? and hence seeing
the stuff done on the far host in the ssh pipe that you
opened onto the remote machine?
local -> rsh far_host -c "do foo" -> far_host
the command actually gets invoked on the far_host, but locally
you get to see the 'remote shell' invocation, since, well,
one actually is 'on the far host' at the time.
> I need to initiate a task on a remote machine and have that task run
> and
> display on the remote machine. The Perl script should initiate then
> ignore
> the remote process.
[..]
The part about 'initiate and ignore' is the part that worries me.
So what exactly do you mean by 'display on the remote machine'?
Where is the STDOUT going to be pointed in that event? to /dev/console?
The more traditional solution is something of the form:
MON_BOX -> message -> host_box
|
V
starter_code -> start daemon process
|
<--return_info <----
|
V
Display Output
Where one does a pipe and exec sequence then reads through
the list of open FD's as info comes back, cf perldoc IO::Select
and then as one needs to 'update' incoming information, one
does that...
ciao
drieux
---
- Next message: Wc -Sx- Jones: "Re: warn ?!"
- Previous message: Paul Johnson: "Re: warn ?!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
