Mel [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
it will either read input or it won't, and what happens when it
reads depends entirely on what the fd it reads from is connected to,
whether it's a slow or fast device, blocking or non-blocking, etc.
The kernel
On Tuesday 01 April 2008 12:14:08 Dag-Erling Smørgrav wrote:
Mel [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
it will either read input or it won't, and what happens when it
reads depends entirely on what the fd it reads from is connected to,
whether it's a
On Mon, 31 Mar 2008, Dag-Erling Smrgrav wrote:
DSMel [EMAIL PROTECTED] writes:
DS
DSEV_SET(changes[0], fileno(proc), EVFILT_WRITE, EV_ADD|EV_ENABLE, 0,
DS0, 0);
DSEV_SET(changes[1], fileno(proc), EVFILT_READ, EV_ADD|EV_ENABLE, 0,
DS0, 0);
DS
DSThis
On Monday 31 March 2008 05:49:33 Dag-Erling Smørgrav wrote:
Mel [EMAIL PROTECTED] writes:
Hi,
from reading the manpage on EVFILT_WRITE I thought it would be an easy to
use interface to detect when a program wants input.
So far, that doesn't seem to be the case. Ultimately what I want to
Hi,
from reading the manpage on EVFILT_WRITE I thought it would be an easy to use
interface to detect when a program wants input.
So far, that doesn't seem to be the case. Ultimately what I want to do is pipe
all the popen(3)'d output to a logfile and act on any input it wants.
Could anyone
Mel [EMAIL PROTECTED] writes:
Hi,
from reading the manpage on EVFILT_WRITE I thought it would be an easy to use
interface to detect when a program wants input.
So far, that doesn't seem to be the case. Ultimately what I want to do is
pipe
all the popen(3)'d output to a logfile and act
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
[...]
Apologies for my atrocious quoting...
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To
7 matches
Mail list logo