It is also possible that it would only write as much as it can,
and return the amount written, leaving it to you to write the rest
later. (Uhm.. you do check the return values from write(2), right? :)
The relevant source is in src/sys/kern/sys_pipe.c, namely the pipe_write()
function. From a
hi all,
pipes uses only direct blocks to store data. so
depending on the blocksize , a total data of
10*blocksize can be written in one go but what happens
if a writer process tries to write more 10*blocksize
of data in one go. Does the kernel overwrites the
data in pipe or not ? if yes,
I guess the kernel will block the process trying to write more data than
that can be accommodated. Or if you are using non-blocking I/O, it will
return an error.
-Zhihui
On Wed, 27 Jun 2001, Manas Bhatt wrote:
hi all,
pipes uses only direct blocks to store data. so
depending on the
3 matches
Mail list logo
