summaryrefslogtreecommitdiffstats
path: root/include/memory.h
diff options
context:
space:
mode:
authorcjc <cjc@FreeBSD.org>2002-08-25 06:05:25 +0000
committercjc <cjc@FreeBSD.org>2002-08-25 06:05:25 +0000
commitabd6ef614697a337ee8fb816784aac80409d0f50 (patch)
tree6a8991654ebbf3ce430d79063c12f548aecad1ce /include/memory.h
parente4a8f19dec8e7787e97565378dda14ef8f6ea854 (diff)
downloadFreeBSD-src-abd6ef614697a337ee8fb816784aac80409d0f50.zip
FreeBSD-src-abd6ef614697a337ee8fb816784aac80409d0f50.tar.gz
Don't give up on a remote log host when we get a EHOSTUNREACH or
EHOSTDOWN. These are often transient errors (when the remote host reboots, temporary network problems, etc.), and we'd rather err on the side of caution and keep trying send messages that never arrive than just give up. Note that this is not an implementation of the "back-off" methods given in the PR. Those just seem too complicated. Why not just keep trying each time? Trying and failing doesn't really consume significantly more resources than if we were successful for each message. PR: bin/31029 MFC after: 1 week
Diffstat (limited to 'include/memory.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud