<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in rc.shutdown</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>46f18ecf8d3cdda1cd433841c44a4c1268ab9721 - rc: Use check_jail to check values of security.jail MIBs</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/rc/rc.shutdown#46f18ecf8d3cdda1cd433841c44a4c1268ab9721</link>
        <description>rc: Use check_jail to check values of security.jail MIBsPR:		282404Reviewed by:	markj, netchildApproved by:	markj (mentor)MFC after:	2 weeksEvent:		Berlin Hackathon 202507Differential Revision:	https://reviews.freebsd.org/D47329

            List of files:
            /freebsd/libexec/rc/rc.shutdown</description>
        <pubDate>Sat, 12 Jul 2025 18:20:32 +0200</pubDate>
        <dc:creator>Mateusz Piotrowski &lt;0mp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>d0b2dbfa0ecf2bbc9709efc5e20baf8e4b44bbbf - Remove $FreeBSD$: one-line sh pattern</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/rc/rc.shutdown#d0b2dbfa0ecf2bbc9709efc5e20baf8e4b44bbbf</link>
        <description>Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/

            List of files:
            /freebsd/libexec/rc/rc.shutdown</description>
        <pubDate>Wed, 16 Aug 2023 19:55:03 +0200</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>7424699c9f94f9ba8ae6991b54608cfc3401a152 - rc.shutdown: kill shutdown process after logging message</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/rc/rc.shutdown#7424699c9f94f9ba8ae6991b54608cfc3401a152</link>
        <description>rc.shutdown: kill shutdown process after logging messageMove the kill -KILL $$ back to the pre-r354446 location at the end ofthe shutdown timeout handler.MFC with:	r354446

            List of files:
            /freebsd/libexec/rc/rc.shutdown</description>
        <pubDate>Sat, 07 Dec 2019 01:33:08 +0100</pubDate>
        <dc:creator>Ed Maste &lt;emaste@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>4a76bd99acb9018721cebc666bf4504be766250b - rc.shutdown: print a newline before watchdog timeout message</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/rc/rc.shutdown#4a76bd99acb9018721cebc666bf4504be766250b</link>
        <description>rc.shutdown: print a newline before watchdog timeout messagePreviously the watchdog timeout message was appended to the last entryin the &quot;Waiting for PIDS&quot; list, resulting in a message like    Waiting for PIDS: 31299 31296 90201 9020090 second watchdog timeout    expired. Shutdown terminated.Print a newline to separate the watchdog timeout message.  Also performthe kill before logging or echoing the message.PR:		241072MFC after:	1 monthSponsored by:	The FreeBSD Foundation

            List of files:
            /freebsd/libexec/rc/rc.shutdown</description>
        <pubDate>Thu, 07 Nov 2019 16:48:46 +0100</pubDate>
        <dc:creator>Ed Maste &lt;emaste@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>8b3bc70a2b2d3889f9163e5e5a24747cea6417e6 - Merge ^/head r352764 through r353315.</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/rc/rc.shutdown#8b3bc70a2b2d3889f9163e5e5a24747cea6417e6</link>
        <description>Merge ^/head r352764 through r353315.

            List of files:
            /freebsd/libexec/rc/rc.shutdown</description>
        <pubDate>Tue, 08 Oct 2019 20:17:02 +0200</pubDate>
        <dc:creator>Dimitry Andric &lt;dim@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>5fda0d60c1e004d6581f29c006635a51cee81349 - add ability to set watchdog timeout for a shutdown</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/rc/rc.shutdown#5fda0d60c1e004d6581f29c006635a51cee81349</link>
        <description>add ability to set watchdog timeout for a shutdownThis change allows to specify a watchdog(9) timeout for a systemshutdown.  The timeout is activated when the watchdogd daemon isstopped.  The idea is to a prevent any indefinite hang during latestages of the shutdown.  The feature is implemented in rc.d/watchdogd,it builds upon watchdogd -x option.Note that the shutdown timeout is not actiavted when the watchdogdservice is individually stopped by an operator.  It is also notactivated for the &apos;shutdown&apos; to the single-user mode.  In those cases itis assumed that the operator knows what they are doing and they havemeans to recover the system should it hang.Significant subchanges and implementation details:- the argument to rc.shutdown, completely unused before, is assigned to  rc_shutdown variable that can be inspected by rc scripts- init(8) passes &quot;single&quot; or &quot;reboot&quot; as the argument, this is not  changed- the argument is not mandatory and if it is not set then rc_shutdown is  set to &quot;unspecified&quot;- however, the default jail management scripts and jail configuration  examples have been updated to pass &quot;jail&quot; to rc.shutdown, just in case- the new timeout can be set via watchdogd_shutdown_timeout rc option- for consistency, the regular timeout can now be set via  watchdogd_timeout rc option- watchdogd_shutdown_timeout and watchdogd_timeout override timeout  specifications in watchdogd_flags- existing configurations, where the new rc options are not set, should  keep working as beforeI am not particularly wed to any of the implementation specifics.I am open to changing or removing any of them as long as the providedfunctionality is the same (or very close) to the proposed one.For example, I think it can be implemented without using watchdogd -x,by means of watchdog(1) alone.  In that case there would be a smallwindow between stopping watchdogd and running watchdog, but I think thatthat is acceptable.Reviewed by:	bcr (man page changes)MFC after:	5 weeksRelnotes:	yesDifferential Revision: https://reviews.freebsd.org/D21221

            List of files:
            /freebsd/libexec/rc/rc.shutdown</description>
        <pubDate>Thu, 03 Oct 2019 13:23:10 +0200</pubDate>
        <dc:creator>Andriy Gapon &lt;avg@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>c6879c6c14eedbd060ba588a3129a6c60ebbe783 - Merge ^/head r339015 through r339669.</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/rc/rc.shutdown#c6879c6c14eedbd060ba588a3129a6c60ebbe783</link>
        <description>Merge ^/head r339015 through r339669.

            List of files:
            /freebsd/libexec/rc/rc.shutdown</description>
        <pubDate>Tue, 23 Oct 2018 23:09:37 +0200</pubDate>
        <dc:creator>Dimitry Andric &lt;dim@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>0696600c41600d80bcd993bfd8e675d0ae6951fe - Move the rc framework out of sbin/init into libexec/rc.</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/rc/rc.shutdown#0696600c41600d80bcd993bfd8e675d0ae6951fe</link>
        <description>Move the rc framework out of sbin/init into libexec/rc.The reasons for this are forward looking to pkgbase: * /sbin/init is a special binary; try not to replace it with   every package update because an rc script was touched.   (a follow-up commit will make init its own package) * having rc in its own place will allow more easy replacement   of the rc framework with alternatives, such as openrc.Discussed with:		brd (during BSDCam), kmooreRequested by:		cem, bzPR:			231522Approved by:		re (gjb)

            List of files:
            /freebsd/libexec/rc/rc.shutdown</description>
        <pubDate>Wed, 17 Oct 2018 18:49:11 +0200</pubDate>
        <dc:creator>Bjoern A. Zeeb &lt;bz@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
