From owner-freebsd-arch@freebsd.org Sun Oct 29 07:26:22 2017 Return-Path: Delivered-To: freebsd-arch@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 AA837E5C21D for ; Sun, 29 Oct 2017 07:26:22 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from know-smtprelay-omc-5.server.virginmedia.net (know-smtprelay-omc-5.server.virginmedia.net [80.0.253.69]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E509D6F45F for ; Sun, 29 Oct 2017 07:26:21 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from [192.168.1.5] ([86.10.211.13]) by know-smtprelay-5-imp with bizsmtp id TKSJ1w00L0HtmFq01KSJgQ; Sun, 29 Oct 2017 07:26:19 +0000 X-Originating-IP: [86.10.211.13] X-Authenticated-User: J.deBoynePollard-newsgroups@NTLWorld.COM X-Spam: 0 X-Authority: v=2.1 cv=XuEHQgx9 c=1 sm=1 tr=0 a=SB7hr1IvJSWWr45F2gQiKw==:117 a=SB7hr1IvJSWWr45F2gQiKw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=zCF0BwDtR6fGmel4gz4A:9 a=QEXdDO2ut3YA:10 Subject: Re: New reboot flag: -c for 'power cycle' References: <01741ade-cd76-3e7a-2b75-0d9984a6ee90@NTLWorld.COM> To: FreeBSD Arch , FreeBSD Hackers From: Jonathan de Boyne Pollard Message-ID: Date: Sun, 29 Oct 2017 07:26:18 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2017 07:26:22 -0000 Warner Losh: > * system-manager now treats SIGWINCH differently on non-Linux > operating systems, treading it as a request to invoke a new > powercycle service. > > SIGRTMIN+6, unused in the systemd system, is the Linux equivalent. > > * system-manager now treats SIGRTMIN+16 as the underlying actual > powercycle request, which it translates to either RB_POWERCYCLE if > it is present in the C library headers, or RB_AUTOBOOT if it is not. > > * There is now a new system-control powercycle subcommand, which > defaults to sending SIGWINCH/SIGRTMIN+6 or SIGRTMIN+16. > > It looks like all the SIGRT* signals are user defined, and can be used > for any purpose by the application. It could easily be SIGRTMIN+6 as > it is SIGWINCH and we could ditch SIGWINCH on FreeBSD in init as well > (since it's only been in -current for a few days). Would that suffice > to address the compatibility concerns? There's no reason to be > gratuitously different here. > True, but it's not my softwares that you and I have to worry about. I've just double checked, and the very thing that my softwares themselves are being compatible with here has already used SIGRTMIN+16 and SIGRTMIN+6, so I am going to adjust to +17 and +7 . I'll let the systemd people know. Let's see what transpires from that.