<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test/libexec/rc, branch main</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test/atom?h=main</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/'/>
<updated>2020-12-18T16:02:28Z</updated>
<entry>
<title>Fix the ipfw service status output when ipfw.ko isn't loaded</title>
<updated>2020-12-18T16:02:28Z</updated>
<author>
<name>Mark Johnston</name>
<email>markj@FreeBSD.org</email>
</author>
<published>2020-12-18T16:02:28Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=5120612664fbc54d69ee1a21d0abcbab58712709'/>
<id>urn:sha1:5120612664fbc54d69ee1a21d0abcbab58712709</id>
<content type='text'>
Reported by:	lme
Reviewed by:	lme
MFC after:	1 week
Differential Revision:	https://reviews.freebsd.org/D27657
</content>
</entry>
<entry>
<title>Make mountcritremote dependent upon nfscbd.</title>
<updated>2020-12-17T00:20:57Z</updated>
<author>
<name>Rick Macklem</name>
<email>rmacklem@FreeBSD.org</email>
</author>
<published>2020-12-17T00:20:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=31b29217abc4da8504df959794d43428712f2666'/>
<id>urn:sha1:31b29217abc4da8504df959794d43428712f2666</id>
<content type='text'>
Although it is not often needed, the nfscbd(8) should be running when
NFSv4 mounts are done if callback functionality is required.
Callback functionality is required for the NFSv4 server to issue
delegations or pNFS layouts.

This patch adds nfscbd to the mountcritremote's REQUIRED line
to ensure it is started before NFS mounts specified in /etc/fstab
are done.

Reviewed by:	0mp
Differential Revision:	https://reviews.freebsd.org/D27506
</content>
</entry>
<entry>
<title>Revert r366857.</title>
<updated>2020-12-04T19:31:16Z</updated>
<author>
<name>Cy Schubert</name>
<email>cy@FreeBSD.org</email>
</author>
<published>2020-12-04T19:31:16Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=353ce816878c17e4367280f178d9cb521cc3d616'/>
<id>urn:sha1:353ce816878c17e4367280f178d9cb521cc3d616</id>
<content type='text'>
r366857 created a number of problems, tearing down interfaces too
early in shutdown. This resulted in:

- hung ssh sessions when shutting down or rebooting remotely using
  shutdown (I've used exec shutdown, for years, as apposed to simply
  shutdown).

- NFS mounted filesystems "disappear" prior to unmount.

- dhclient attached to a VLAN on an interface who's parent interface
  has already shut down prints errors.

The path forward is to teach lagg(4) and vlan(4) about WOL.

PR:		251531, 251540
PR:		158734, 109980 are broken again
Reported by:	jhb, emaste, jtl, Helge Oldach&lt;freebsd_oldach.net&gt;
		Martin Birgmeier &lt;d8zNeCFG_aon.at&gt;
MFC after:      Immediately
Discussion at:	https://reviews.freebsd.org/D27459
</content>
</entry>
<entry>
<title>IPv6: set ifdisabled in the kernel rather than in rc</title>
<updated>2020-11-25T20:58:01Z</updated>
<author>
<name>Bjoern A. Zeeb</name>
<email>bz@FreeBSD.org</email>
</author>
<published>2020-11-25T20:58:01Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=dd4d5a5ffbfa65b61d30b3bfac0e09a75a8cbe3b'/>
<id>urn:sha1:dd4d5a5ffbfa65b61d30b3bfac0e09a75a8cbe3b</id>
<content type='text'>
Enable ND6_IFF_IFDISABLED when the interface is created in the
kernel before return to user space.

This avoids a race when an interface is create by a program which
also calls ifconfig IF inet6 -ifdisabled and races with the
devd -&gt; /etc/pccard_ether -&gt; .. netif start IF -&gt; ifdisabled
calls (the devd/rc framework disabling IPv6 again after the program
had enabled it already).

In case the global net.inet6.ip6.accept_rtadv was turned on,
we also default to enabling IPv6 on the interfaces, rather than
disabling them.

PR:		248172
Reported by:	Gert Doering (gert greenie.muc.de)
Reviewed by:	glebius (, phk)
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D27324
</content>
</entry>
<entry>
<title>Revert r367291 (KEYWORD: shutdown for rc.d/zfs)</title>
<updated>2020-11-20T14:37:07Z</updated>
<author>
<name>Mateusz Piotrowski</name>
<email>0mp@FreeBSD.org</email>
</author>
<published>2020-11-20T14:37:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=e5912dcf20718573bdb694b085d1cf3bc10a2eb5'/>
<id>urn:sha1:e5912dcf20718573bdb694b085d1cf3bc10a2eb5</id>
<content type='text'>
The problem is that zfs is asked to stop too early in the shutdown
sequence. Other services, such as syslog may still be running and have some
files open (e.g., under /var/log). This of course causes the messages like:

  cannot unmount '/var/run': umount failed
  cannot unmount '/var/log': umount failed
  cannot unmount '/var': umount failed
  cannot unmount '/usr/home': umount failed
  cannot unmount '/usr': umount failed
  cannot unmount '/': umount failed

For now, let's remove the shutdown KEYWORD from the zfs service, as people are
reporting problems in their setups:
https://lists.freebsd.org/pipermail/freebsd-current/2020-November/077559.html

In the future, we may think of stopping zfs on shutdown after all the other
services and just before init(8) exits. Another interesting option might be to
a new rcorder(8) KEYWORD like "shutdownjail", but this idea would need to be
discussed a bit.

Reported by:	Johan Hendriks &lt;joh.hendriks gmail.com&gt;
Reported by:	Yasuhiro KIMURA &lt;yasu utahime.org&gt;
Reported by:	Tomoaki AOKI &lt;junchoon dec.sakura.ne.jp&gt;
Approved by:	kevans (src)
MFC:		3 days
Differential Revision:	https://reviews.freebsd.org/D27263
</content>
</entry>
<entry>
<title>Fix startup of gssd when /usr is a separately mounted local file system.</title>
<updated>2020-11-14T01:49:49Z</updated>
<author>
<name>Rick Macklem</name>
<email>rmacklem@FreeBSD.org</email>
</author>
<published>2020-11-14T01:49:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=01b139f212a11d78b6cba95340404f03a9f3c418'/>
<id>urn:sha1:01b139f212a11d78b6cba95340404f03a9f3c418</id>
<content type='text'>
meowthink@gmail.com reported that the gssd daemon was not
starting, because /etc/rc.d/gssd was executed before his local
/usr file system was mounted.
He fixed the problem by adding mountcritlocal to the REQUIRED
line.

This fix seems safe and works for a separately mounted /usr file
system on a local disk.
The case of a separately mounted remote /usr file system (such as
NFS) is still broken, but there is no obvious solution for that.
Adding mountcritremote would fix the problem, but it would
cause a POLA violation, because all kerberized NFS mounts
in /etc/fstab would need the "late" option specified to work.

Submitted by:	meowthink@gmail.com
Reported by:	meowthink@gmail.com
Reviewed by:	0mp
MFC after:	2 weeks
Relnotes:	yes
Differential Revision:	https://reviews.freebsd.org/D27203
</content>
</entry>
<entry>
<title>Add support for the new mountd -R option.</title>
<updated>2020-11-06T16:33:42Z</updated>
<author>
<name>Rick Macklem</name>
<email>rmacklem@FreeBSD.org</email>
</author>
<published>2020-11-06T16:33:42Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=4389a5661034536b423181476cbbc6efca825055'/>
<id>urn:sha1:4389a5661034536b423181476cbbc6efca825055</id>
<content type='text'>
r376026 added a new "-R" option to mountd, which tells it to
not support the Mount protocol (not used by NFSv4) and not
register with rpcbind.
Rpcbind is considered a security issue by some sites now.

This patch adds a new yes/no variable called nfsv4_server_only.
When that is set, make vfs.nfsd.server_min_vers=4 and set "=R"
for mountd.
Setting vfs.nfsd.server_min_vers=4 tells nfsd to not register with rpcbind.
While here, add a check for "load_kld nfsd" failing to nfsd.

Reviewed by:	0mp
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D26938
</content>
</entry>
<entry>
<title>Replace literal uses of /usr/local with a variable</title>
<updated>2020-11-03T12:29:10Z</updated>
<author>
<name>Stefan Eßer</name>
<email>se@FreeBSD.org</email>
</author>
<published>2020-11-03T12:29:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=08867050c9339cd21d4ca1ea12ad88e37db1f60e'/>
<id>urn:sha1:08867050c9339cd21d4ca1ea12ad88e37db1f60e</id>
<content type='text'>
The variable defaults to "/usr/local", unless sysctl returns some other
value for "user.localbase".

The value of user.localbase defaults to _PATH_LOCALBASE as defined in
paths.h and thus this commit has no immediate effect.

The purpose of this change is to make /etc/defaults/rc.conf automatically
use the value of _PATH_LOCALBASE when not set to the default value.

Reviewed by:	imp, scottl
MFC after:	1 month
Differential Revision:	https://reviews.freebsd.org/D27014
</content>
</entry>
<entry>
<title>rc.d/zfs: Add shutdown to KEYWORDS</title>
<updated>2020-11-03T10:02:52Z</updated>
<author>
<name>Mateusz Piotrowski</name>
<email>0mp@FreeBSD.org</email>
</author>
<published>2020-11-03T10:02:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=0cadbd6cd258e2a889c49f42d3f61f85663eeb75'/>
<id>urn:sha1:0cadbd6cd258e2a889c49f42d3f61f85663eeb75</id>
<content type='text'>
The problem is that Without walling /etc/rc.d/zfs on shutdown, resources
associated with ZFS mounts are not freed and the jails will remain in dying
state. In addition, the dataset is now in a dangling state, as the jail it
is attached to is dying.

A known workaround for jails was to add the following lines
to /etc/jail.conf, to make sure that "service zfs stop" is run
when the jail is stopped:

    exec.stop = "/bin/sh /etc/rc.shutdown";
    exec.stop += "/usr/sbin/service zfs stop || /usr/bin/true";

While the workaround seems to be okay-ish for the jail situation, it is
still unclean. However, for physical hosts this may wreak havoc with the
pool if shared spares are used, as "zfs unshare" is never invoked on
shutdown.

PR:		147444
Submitted by:	Markus Stoff &lt;markus__stoffdv_at&gt;
Reported by:	Mykah &lt;mburkhardt__exavault_com&gt;
Reviewed by:	cy
Approved by:	cy (src)
MFC after:	1 week
Relnotes:	yes
Differential Revision:	https://reviews.freebsd.org/D27039
</content>
</entry>
<entry>
<title>rc.d/syscons: remove spaces before tab</title>
<updated>2020-10-25T18:27:21Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2020-10-25T18:27:21Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=98b04ac35965fa0735c06a4966c6939f8009509e'/>
<id>urn:sha1:98b04ac35965fa0735c06a4966c6939f8009509e</id>
<content type='text'>
</content>
</entry>
</feed>
