Hello,
>Definitely reproduced under 2.0.35-pre15, although I haven't been able
>to force it on 2.1.
>
>> Is there any improper part in this program? Or, is there
>> any other way to read from "stdout" asynchronously?
>
>The only problem in your code is that it is doing something unusual:
>there is no bug. It seems that the buffered IO routines are generating
>much larger IO requests than the kernel can deal with atomically. If
>you used unbuffered IO (read(2) and write(2) directly) and limited the
>size of the IOs, you'd probably not see the problem (although it IS
>still a kernel bug if the user's program ever gets this).
Thank you for all your help.
The function "read_and_write()" in my test program is a temporary function.
In the target server program, this function corresponds to the interpreter
function in Python library which is being distributed in "www.python.org".
The interpreter function returns only status, and does not return the data
such as text and numeric data retrieved from RDB by a script.
So I make the server program read the data written to "stdout" by
a script asynchronously.
I would not like to restrict the way to write the data to "stdout"
in a script, because a script is also written by other users.
Originally I had written this server program under Solaris 2.x, and it has
been working well. The test program also works under Solaris 2.x or
FreeBSD 2.2.6. But there is a problem under Linux. So I was thinking
my test program including some improper part, or it was due to the kernel bug.
How do you think about the difference between those actions which occurred
when I ran the almost same programs under different OSes?
P.S.
I have run the test program under following version of Linux kernel
and libc. In every case, the same error has ocurred.
Kernel-2.0.33, libc-5.3.12
Kernel-2.0.35, libc-5.4.33
Kernel-2.0.34, libc-5.4.44
Kernel-2.0.35, glibc-2.0.7
Regards,
Masahiko Shimoda
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
