Date: Tue, 22 Apr 2014 02:30:01 GMT From: Mark Linimon <linimon@lonesome.com> To: freebsd-standards@FreeBSD.org Subject: Re: standards/164793: [libc] write(2) system call violates POSIX standard Message-ID: <201404220230.s3M2U1XX092371@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR standards/164793; it has been noted by GNATS. From: Mark Linimon <linimon@lonesome.com> To: bug-followup@FreeBSD.org Cc: Subject: Re: standards/164793: [libc] write(2) system call violates POSIX standard Date: Mon, 21 Apr 2014 21:21:14 -0500 ----- Forwarded message from Bruce Evans <brde@optusnet.com.au> ----- Date: Mon, 21 Apr 2014 16:24:52 +1000 (EST) From: Bruce Evans <brde@optusnet.com.au> To: linimon@freebsd.org Subject: Re: standards/164793: [libc] write(2) system call violates POSIX standard On Sun, 20 Apr 2014 linimon@freebsd.org wrote: > Old Synopsis: 'write' system call violates POSIX standard > New Synopsis: [libc] write(2) system call violates POSIX standard Should be '[kern]'. I see I wrote too much in the followup. The PR is mostly about RLIMIT_FSIZE not working, and this also affects ftruncate() and truncate(), and is is probably fs-dependent with zfs and fusefs possibly not having it, so write(2) is not very descriptive either. > Responsible-Changed-From-To: freebsd-bugs->freebsd-standards This is correct. Bruce ----- End forwarded message -----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404220230.s3M2U1XX092371>