Date: Wed, 5 Jun 2002 08:43:03 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Alexander Leidinger <netchild@FreeBSD.ORG> Cc: audit@FreeBSD.ORG, Benjamin Lewis <bhlewis@wossname.net> Subject: Re: [PATCH] making dump EINTR resistant Message-ID: <20020605083335.T5376-100000@gamplex.bde.org> In-Reply-To: <200206040907.g54975wE003913@Magelan.Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 4 Jun 2002, Alexander Leidinger wrote: > Benjamin Lewis <bhlewis@wossname.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020605083335.T5376-100000>