Date: Mon, 12 Aug 2002 16:15:35 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Bruce Evans <bde@zeta.org.au> Cc: Bob Willcox <bob@immure.com>, Ian Dowse <iedowse@maths.tcd.ie>, Alexander Leidinger <Alexander@leidinger.net>, bhlewis@wossname.net, freebsd-current@FreeBSD.ORG Subject: Re: Is anyone else having trouble with dump(8) on -current? Message-ID: <3D584197.44EE0075@mindspring.com> References: <20020813055009.N25992-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans wrote: > > >From my experience/use with amanda I know that it _always_ kills the > > dumps that it starts when doing its estimates at the beginning (often > > several per file system, one for each dump level it's interested in). I > > don't think it deliberately kills the dumps when actually dumping the > > data. :-) > > So the problem seems to be mainly that dump expects all syscalls to be > restarted after it catches these signals, and open() isn't restarted. POSIX sucks... siginterrupt(3) is your friend, in this case. Unfortunately, someone broke it and added a "sig" parameter, and you have to call it once per signal now, which means enumerating signals on an unknown host system (brilliant engineering, that). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D584197.44EE0075>