tree 6f8ffd3a083bee4c8c8fa2b4e2eb5981b4af1cbe
parent 9e47abd862f71847a85f330435c7b3a9b1f76099
author David Lamparter <equinox@opensourcerouting.org> 1375274381 +0200
committer David Lamparter <equinox@opensourcerouting.org> 1375274664 +0200

bgpd: write NOTIFY non-blockingly

switching the socket to blocking may well block the entire bgpd process
for some time if our peer is overloaded (which may well be the original
reason for the NOTIFY)

The error handling is slightly different from the previous ML discussion
on this;  buffer exhaustion isn't technically a fatal TCP error, and we
should probably proceed with FSM actions according to a sent NOTIFY
(adjusting timers) even if we didn't manage to get the NOTIFY onto the
wire.

Acked-by: Leonid Rosenboim <lrosenbo@wrs.com>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>