On Sat, Aug 28, 2010 at 06:42:29PM +0400, Anonymous wrote:
> Alexander Best writes:
> > i just had subversion complain about a broken pipe while piping its
> > output through awk straight to head [1]. i decided to add a switch
> > to head which will tell it to never close a pipe unless the input
On 08/28/2010 12:01, Alexander Best wrote:
> On Sat Aug 28 10, Anonymous wrote:
>> Alexander Best writes:
>>
>>> hi there,
>>>
>>> i just had subversion complain about a broken pipe while piping its output
>>> through awk straight to head [1]. i decided to add a switch to head which
>>> will
>>>
On Sat Aug 28 10, Anonymous wrote:
> Alexander Best writes:
>
> > hi there,
> >
> > i just had subversion complain about a broken pipe while piping its output
> > through awk straight to head [1]. i decided to add a switch to head which
> > will
> > tell it to never close a pipe unless the input
Anonymous writes:
> Alexander Best writes:
>
>> hi there,
>>
>> i just had subversion complain about a broken pipe while piping its output
>> through awk straight to head [1]. i decided to add a switch to head which
>> will
>> tell it to never close a pipe unless the input has stopped [2].
>
>
Alexander Best writes:
> hi there,
>
> i just had subversion complain about a broken pipe while piping its output
> through awk straight to head [1]. i decided to add a switch to head which will
> tell it to never close a pipe unless the input has stopped [2].
You can do same with sh(1), e.g.
hi there,
i just had subversion complain about a broken pipe while piping its output
through awk straight to head [1]. i decided to add a switch to head which will
tell it to never close a pipe unless the input has stopped [2].
of course this will produce massive overhead, but some people might f
6 matches
Mail list logo
