From owner-freebsd-standards@FreeBSD.ORG Tue Mar 22 14:57:36 2011 Return-Path: Delivered-To: freebsd-standards@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABCB0106566C for ; Tue, 22 Mar 2011 14:57:36 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2AEFA8FC21 for ; Tue, 22 Mar 2011 14:57:35 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id p2MEvJAV035859; Tue, 22 Mar 2011 15:57:34 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id p2MEvJub035858; Tue, 22 Mar 2011 15:57:19 +0100 (CET) (envelope-from olli) Date: Tue, 22 Mar 2011 15:57:19 +0100 (CET) Message-Id: <201103221457.p2MEvJub035858@lurza.secnetix.de> From: Oliver Fromme To: freebsd-standards@FreeBSD.ORG, utisoft@gmail.com, Maxim Konovalov In-Reply-To: X-Newsgroups: list.freebsd-standards User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Tue, 22 Mar 2011 15:57:35 +0100 (CET) Cc: Subject: Re: dd dies on SIGUSR1 X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-standards@FreeBSD.ORG, utisoft@gmail.com, Maxim Konovalov List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2011 14:57:36 -0000 Chris Rees wrote: > Maxim Konovalov wrote: > > FreeBSD uses SIGINFO for such purposes for ages in many programs > > apart from dd(1).  IMHO, nothing to fix here. > > Of course, and I'm not suggesting that FreeBSD is wrong in any way. > > My point was that it was rather a harsh punishment for using a GNU-ism > where dd died after 30 minutes of chugging or so. Well, when it died, it did exactly what you told it to: Terminating the process is the default action for SIGUSR1, see signal(3), and the dd(1) manpage doesn't mention that SIGUSR1 is used for anything (in rather states that SIGINFO is used for the purpose that you intended), so the default action applies. I tend to agree with Maxim here. > Would it hurt for dd to ignore the signal rather than die? I imagine a > lot less than otherwise. But then -- for consistency -- you would have to apply the same patch to *all* programs that use SIGINFO, such as dump and tar. And what should be done if a program uses SIGINFO for status display *and* SIGUSR1 for something completely unrelated, such as ftp(1)? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "That's what I love about GUIs: They make simple tasks easier, and complex tasks impossible." -- John William Chambless