From owner-freebsd-bugs@freebsd.org Mon Sep 19 22:02:40 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F8ADBE0732 for ; Mon, 19 Sep 2016 22:02:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 24EDD615 for ; Mon, 19 Sep 2016 22:02:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8JM2dmq090241 for ; Mon, 19 Sep 2016 22:02:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 212829] daemon(8) using -P swallows signals such as SIGHUP instead of propagating them Date: Mon, 19 Sep 2016 22:02:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: prj@rootwyrm.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 22:02:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212829 prj@rootwyrm.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |prj@rootwyrm.com --- Comment #1 from prj@rootwyrm.com --- To elaborate on my general thoughts; The issue with just passing signals through daemon is: what if we want to signal daemon? Whoops. The other possibility is to use uncommonly used sign= als but then all you've got is SIGUSR1 and SIGUSR2 without violating sanity. Obviously, that is not an acceptable solution either.=20 So my thought is that a user who wishes for daemon(8) to pass signals to the child needs to provide two explicit arguments at runtime. First, the existi= ng child pid argument -p. Second, the flag -s 'signal passing.' This would tell daemon to simply pass through all signals verbatim to the PID contained wit= hin -p. (-s would conflict with -r as well.) This means it's an explicit user-initiated behavior change, rather than function change. Obviously, this then presents the problem: how to signal daemon itself. Tha= t I do not have an elegant solution for. My initial thought was to have a socket equivalent to -P where the user could simply echo the desired signal number= to. e.g. "echo '9' > /var/run/daemon/234.pid" - which isn't exactly optimal eit= her. However, this might be a more workable solution for child signalling perhap= s? Thoughts and feedback definitely appreciated. --=20 You are receiving this mail because: You are the assignee for the bug.=