Re: kgio_trywrite raises "Broken pipe - send (Errno::EPIPE)"

["Iñaki Baz Castillo" <ibc@aliax.net>]

2012/4/10 Eric Wong <normalperson@yhbt.net>:
> Iñaki Baz Castillo <ibc@aliax.net> wrote:
>> Hi, I've realized that in certain cases Kgio::TCPSocket#kgio_trywrite
>> raises a "Broken pipe - send (Errno::EPIPE)" exception.
>
> EPIPE means the reader got closed or died somehow.  EPIPE is uncommon
> in normal use, but it is fatal and not possible to recover from (unlike
> EAGAIN).

Sure, what I mean is that kgio_trywrite could return :error_epipe so I
would terminate the socket and so :)



> kgio already skips the expensive backtrace generation for
> EPIPE/ECONNRESET since there's nothing the programmer can do about it in
> non-buggy code, though.  (An attacker can trigger EPIPE/ECONNRESET,
> though, so this adds a _small_ amount of DoS protection)

Opss:

  rescue => e
    puts "#{e.class}: #{e.message}"
    puts "backtrace: #{e.backtrace.inspect}"

Result:

  Errno::ECONNRESET: Connection reset by peer - recv> -
  backtrace: ""


Good :)

-- 
Iñaki Baz Castillo
<ibc@aliax.net>