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.
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 implem
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 han
On Mon, 2008-11-03 at 18:48 +, Brian L. Stuart 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
> > > 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
> > 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 di
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
> 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 ki
On Mon, 2008-11-03 at 08:03 -0500, erik quanstrom wrote:
> > what is the point of reading /proc/n/ note for anything but a
> > stopped/borken process?
>
> or a process already in a note handler?
Could you elaborate, please? Do you mean that if the process
enters its note handler, then the sure fi
> I've been experimenting with how Plan 9 handles notes for processes and
> I must confess that I'm now confused and in need your help.
>
> First of all, the proc(3) man page says that "A read [from /proc/n/
> note] of at least ERRLEN
> characters will retrieve the oldest note posted to the proce
Guys,
I've been experimenting with how Plan 9 handles notes for processes and
I must confess that I'm now confused and in need your help.
First of all, the proc(3) man page says that "A read [from /proc/n/
note] of at least ERRLEN
characters will retrieve the oldest note posted to the process a
11 matches
Mail list logo
