Re: NFS issues since upgrading to 13-RELEASE

Olav, Does anything change if you set -tso -lro on the serving NIC on your FreeBSD server side? Do the Linux clients remain responsive then? I had seen something similar with a Ubuntu 20.04 client going to a 13.0-CURRENT/STABLE server but chalked it up to it starting around the time of the last

catch-all daemon.info entry in syslog.conf is a bit unhelpful

I understand it's been quite some time since it was added, but I have been bitten by it just now. I am adding per-daemon .conf files for ports in /usr/local/etc/syslog.d/ and noticed that none of them were working. An example entry is: $ cat /usr/local/etc/syslog.d/dhcpd.conf !dhcpd *.* /var

Re: catch-all daemon.info entry in syslog.conf is a bit unhelpful

Yuri Pankov wrote: > I understand it's been quite some time since it was added, but I have > been bitten by it just now. I am adding per-daemon .conf files for > ports in /usr/local/etc/syslog.d/ and noticed that none of them were > working. > > An example entry is: > > $ cat /usr/local/etc/sysl

Review D28062 of /usr/src/UPDATING with regard to upgrading FreeBSD and inconsistency with the FreeBSD Handbook

1) lines 2273 and 2275 With ZFS in the mix, /usr/src is present but empty (the file system is not mounted). If single user mode is recommended, then why is this not in the FreeBSD Handbook?