|
Description
|
When reading from a named pipe, the caller passes a maximum read size
of something like 4k, and the read typically returns something smaller.
The return value at user-level should be the amount actually read, but
currently is the requested size.
This problem is not currently exposed because we don't have anything
useing our named pipe support right now. (but we will soon)
|