Zachary Miller wrote:
> If write() is interrupted by a signal after it successfully writes
> some data, it shall return the number of bytes written.
>
> consider SIGSTOP, which is non-maskable. when the process continues, wouldn't
> this be a situation where the write was interrupted and thus
On Tue, Jan 17, 2012 at 10:18:00PM -0500, Chet Ramey wrote:
> On 1/17/12 10:05 PM, Zachary Miller wrote:
> >> Thanks for the report. As a practical matter, this doesn't present a
> >> problem. When writing to a regular file, with no special flags supplied
> >> to open(), the only cases Posix says
On 1/17/12 10:05 PM, Zachary Miller wrote:
>> Thanks for the report. As a practical matter, this doesn't present a
>> problem. When writing to a regular file, with no special flags supplied
>> to open(), the only cases Posix says it can return fewer bytes than
>> specified are errors.
>
> thank
> Thanks for the report. As a practical matter, this doesn't present a
> problem. When writing to a regular file, with no special flags supplied
> to open(), the only cases Posix says it can return fewer bytes than
> specified are errors.
thank chet. i figured that may be the case. if you woul
On 1/17/12 7:04 PM, Zachary Miller wrote:
>
> hello,
>
> i would like to report a what i believe to be a minor bug in bash 4.2 that has
> to do with file redirection:
>
> in redir.c:356 (function write_here_document()), this block of code:
> if (write (fd, document, document_len) < documen
