peter 6adfc2e8bc 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...		1998-08-01 09:04:02 +00:00
..
bootp_subr.c
krpc_subr.c
krpc.h
nfs_bio.c
nfs_common.c
nfs_common.h
nfs_node.c
nfs_nqlease.c
nfs_serv.c
nfs_socket.c	If we get an ENOBUFS from the network, it's normally transient network	1998-08-01 09:04:02 +00:00
nfs_srvcache.c	Moved `#ifndef NFS_NOSERVER' after including nfs.h.	1998-07-02 12:41:42 +00:00
nfs_subs.c
nfs_syscalls.c
nfs_vfsops.c
nfs_vnops.c	VOP_STRATEGY grows an (struct vnode *) argument	1998-07-04 20:45:42 +00:00
nfs.h
nfsdiskless.h
nfsm_subs.h
nfsmount.h
nfsnode.h
nfsproto.h
nfsrtt.h
nfsrvcache.h
nfsv2.h
nqnfs.h	Use u_int32_t in NQFHHASH instead of u_long.	1998-07-05 10:13:22 +00:00
rpcv2.h
xdr_subs.h