From nobody Sun Dec 07 00:49:04 2025 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dP62605C5z6Jxxf for ; Sun, 07 Dec 2025 00:49:18 +0000 (UTC) (envelope-from sr@genyosha.net) Received: from ns1.genyosha.net (ns1.genyosha.net [50.39.243.221]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "cerebus.home.genyosha.net", Issuer "cerebus.home.genyosha.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dP6254LcLz3CsP for ; Sun, 07 Dec 2025 00:49:17 +0000 (UTC) (envelope-from sr@genyosha.net) Authentication-Results: mx1.freebsd.org; none Received: from dragon.home.genyosha.net (ops0.genyosha.net [50.39.243.219]) by ns1.genyosha.net (8.18.1/8.18.1) with ESMTPS id 5B70n9g8007057 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Sat, 6 Dec 2025 16:49:10 -0800 (PST) (envelope-from sr@genyosha.net) Received: from dragon.home.genyosha.net (localhost [127.0.0.1]) by dragon.home.genyosha.net (8.18.1/8.18.1) with ESMTPS id 5B70n4df007158 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 6 Dec 2025 16:49:04 -0800 (PST) (envelope-from sr@dragon.home.genyosha.net) Received: (from sr@localhost) by dragon.home.genyosha.net (8.18.1/8.18.1/Submit) id 5B70n49O007157; Sat, 6 Dec 2025 16:49:04 -0800 (PST) (envelope-from sr) Date: Sat, 6 Dec 2025 16:49:04 -0800 From: Steve Rikli To: infoomatic Cc: freebsd-questions@freebsd.org Subject: Re: 15.0 - rc.conf ignores a setting Message-ID: References: <36931554-9204-46b1-820e-aece55bdf7f8@gmx.at> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <36931554-9204-46b1-820e-aece55bdf7f8@gmx.at> X-Greylist: inspected by milter-greylist-4.6.4 (ns1.genyosha.net [50.39.243.221]); Sat, 06 Dec 2025 16:49:10 -0800 (PST) for IP:'50.39.243.219' DOMAIN:'ops0.genyosha.net' HELO:'dragon.home.genyosha.net' FROM:'sr@genyosha.net' RCPT:'' X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (ns1.genyosha.net [50.39.243.221]); Sat, 06 Dec 2025 16:49:10 -0800 (PST) X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dP6254LcLz3CsP On Sun, Dec 07, 2025 at 12:53:44AM +0100, infoomatic wrote: > I have a pkgbase 15.0 which ignores the new setting precious_machine="YES" > in rc.conf. It does not happen on non-pkgbase 15.0 systems. What could be > the problem? What command and flags are you using to try shutdown the system? Does the behavior change if you manually create the /var/run/noshutdown file? E.g. when I 'touch /var/run/noshutdown' on a 15.0 test VM it properly prevents shutdown with the message "Shutdown cannot be done, /var/run/noshutdown is present". I'm guessing your system's shutdown binary doesn't have the noshutdown function somehow -- is your system from an upgrade or a fresh install? A quick way to check the binary itself: $ strings /sbin/shutdown | grep noshutdown Shutdown cannot be done, /var/run/noshutdown is present /var/run/noshutdown If you don't see that sort of output, I think that shows why you have the problem, but not necessarily how it got that way. Cheers, sr.