From owner-cvs-all  Sat Aug  1 02:04:07 1998
Return-Path: <owner-cvs-all>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA21412
          for cvs-all-outgoing; Sat, 1 Aug 1998 02:04:07 -0700 (PDT)
          (envelope-from owner-cvs-all)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21395;
          Sat, 1 Aug 1998 02:04:03 -0700 (PDT)
          (envelope-from peter@FreeBSD.org)
From: Peter Wemm <peter@FreeBSD.ORG>
Received: (from peter@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id CAA26886;
	Sat, 1 Aug 1998 02:04:02 -0700 (PDT)
Date: Sat, 1 Aug 1998 02:04:02 -0700 (PDT)
Message-Id: <199808010904.CAA26886@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject: cvs commit: src/sys/nfs nfs_socket.c
Sender: owner-cvs-all@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

peter       1998/08/01 02:04:02 PDT

  Modified files:
    sys/nfs              nfs_socket.c 
  Log:
  If we get an ENOBUFS from the network, it's normally transient network
  interface congestion (eg: nfs over a ppp link, etc).  Don't log these
  for UDP mounts, and don't cause syscalls to fail with EINTR.
  This stops the 'nfs send error 55' warnings.
  
  If the error is because the system is really hosed, this is the least
  of your problems...
  
  Revision  Changes    Path
  1.43      +11 -1     src/sys/nfs/nfs_socket.c