On Nov 4, 2008, at 9:16 PM, ron minnich wrote:
On Tue, Nov 4, 2008 at 9:05 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:
On Nov 3, 2008, at 9:41 AM, [EMAIL PROTECTED] wrote:
Frankly, I was trying to see whether an external process reading
on somebody else's /proc/n/note would make any sense. One thing
that I wanted to implement was a "note thief" process that would
constantly read on a target's /proc/n/note and handle the notes
externally using a different kind of IPC to communicate with
the target.
Why?
What I want is to explore a possibility of managing the processes
running
on remote machines via a proxy process (think client side of cpu(1))
running on a terminal.
can you not just import /proc from that machine?
For a single remote process the answer is most likely "yes", but in
reality
your remote process (think a cpu-server side of cpu(1)) is almost
guaranteed
to fan itself out into a bunch of children. And then /proc/n/notepg
becomes
a real pain.
Thanks,
Roman.
P.S. It is actually a bit of a pain even for a single process if I want
things like rio(1) to be able to send signals to the remote side.
I believe that's partially the reason why cpu(1) has to establish
its covert channel for notes via registering a real catcher and
sending notes to a syntehtic filesystem. Which is, if you ask me,
a bit of a statement that notepg might actually belong to some other
place not each /proc/n/
