From owner-freebsd-questions@FreeBSD.ORG Wed Aug 17 14:10:39 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63E7216A41F for ; Wed, 17 Aug 2005 14:10:39 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC7D643D45 for ; Wed, 17 Aug 2005 14:10:19 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 31255 invoked from network); 17 Aug 2005 14:10:18 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 17 Aug 2005 14:10:18 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id A7C7836; Wed, 17 Aug 2005 10:10:17 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Heinrich Rebehn References: <4303180D.8080209@ant.uni-bremen.de> From: Lowell Gilbert Date: 17 Aug 2005 10:10:17 -0400 In-Reply-To: <4303180D.8080209@ant.uni-bremen.de> Message-ID: <44vf24ejsm.fsf@be-well.ilk.org> Lines: 12 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: 2. try: nfsd send error -1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 14:10:39 -0000 Heinrich Rebehn writes: > Aug 17 12:15:11 antsrv1 kernel: nfsd send error -1 > Aug 17 12:15:11 antsrv1 last message repeated 8 times > > I got several of theese errors in my /var/log/messages. Can someone > tell me what this means? The socket send syscall got interrupted (by a signal, maybe?). It should be restartable, but I don't see whether it gets handled, so apparently the kernel just ignores it.