From owner-freebsd-audit Tue Jun 4 18:10:54 2002 Delivered-To: freebsd-audit@freebsd.org Received: from xerxes.courtesan.com (courtesan.com [206.168.103.86]) by hub.freebsd.org (Postfix) with ESMTP id BA57537B411; Tue, 4 Jun 2002 18:10:49 -0700 (PDT) Received: from xerxes.courtesan.com (IDENT:millert@localhost.courtesan.com [127.0.0.1]) by xerxes.courtesan.com (8.12.4/8.12.4) with ESMTP id g551Alpu020379; Tue, 4 Jun 2002 19:10:47 -0600 (MDT) Message-Id: <200206050110.g551Alpu020379@xerxes.courtesan.com> To: Garance A Drosihn Cc: Bruce Evans , Alexander Leidinger , audit@FreeBSD.ORG Subject: Re: [PATCH] making dump EINTR resistant In-reply-to: Your message of "Tue, 04 Jun 2002 19:47:10 EDT." References: <20020605083335.T5376-100000@gamplex.bde.org> Date: Tue, 04 Jun 2002 19:10:47 -0600 From: "Todd C. Miller" 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 In message so spake Garance A Drosihn (drosih): > Would it be acceptable to add EINTR-type checks to freebsd-ish > code? There are some sections of lpr/lpd which do not work > right when compiled on other platforms, unless I add EINTR > checks at the right places. It would probably be better to just make the code in question to just use sigaction() if you are concerned about portability. That way you get consistent handling of syscall restarts. Alternately, you could #define signal to bsd_signal when compiling on non-BSD platforms. That is not quite as portable though. - todd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message