From owner-freebsd-audit Tue Jun 4 15:39:21 2002 Delivered-To: freebsd-audit@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 39F9C37B400; Tue, 4 Jun 2002 15:39:17 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id IAA13730; Wed, 5 Jun 2002 08:39:13 +1000 Date: Wed, 5 Jun 2002 08:43:03 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Alexander Leidinger Cc: audit@FreeBSD.ORG, Benjamin Lewis Subject: Re: [PATCH] making dump EINTR resistant In-Reply-To: <200206040907.g54975wE003913@Magelan.Leidinger.net> Message-ID: <20020605083335.T5376-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 4 Jun 2002, Alexander Leidinger wrote: > Benjamin Lewis had some problems with dump, have > a look at the -current archives (Subject: "Is anyone else having trouble > with dump(8) on -current?", around May 15.). > > I had such a problem on 4.x (perhaps 4.2 or 4.3) once too (I wasn't able > to reproduce it, Benjamin is able to reproduce it on -current) and wrote > the attached patch to solve the problem. Since I wrote it for 4.x, it > runs fine (actually on a 4.4 system which does daily backups to a spare > harddisk). Benjamin uses it also on a daily basis on -current. > > The attached diff is against -current. > > Comments? read(), etc., are supposed to be restarted after signals, so the EINTR checks should have no effect in most cases. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message