Re: writev() "bug"

Aaron Ucko (UCKO@vax1.rockhurst.edu)
Mon, 03 Jun 1996 12:23:25 -0600 (CST)

>> Not necessary. As of libc 5.2.18, libc writev()s longer vectors MAX_IOVEC
>> iov's at a time. The only problem occurs when you use a library compiled
>
>Then libc is broke writev/readv makes atomicity guarantees.

Well, it was even worse before the syscall existed, since then it could
do only 1 iov at a time.

-- Aaron Ucko (ucko@vax1.rockhurst.edu; finger for PGP public key) | httyp!
"That's right," he said. "We're philosophers. We think, therefore we am."
-- Terry Pratchett, _Small Gods_ | Geek Code 3.1 [for explanation, finger
hayden@mankato.msus.edu]: GCS/M/S/C d- s: a18 C++(+++)>++++ UL++>++++ P++
L++>+++++ E- W(-) N++(+) o+ K- w--- O M@ V-(--) PS++(+++) PE- Y(+) PGP(+) t(+)
!5 X-- R(-) tv-@ b++(+++) DI+ !D-- G++(+++) e->+++++(*) h!>+ r-(--)>+++ y?