Re: 11.3->12.1 upgrade, pwd db not rehashed after adding ntpd user?
On Wed, Dec 11, 2019 at 05:44:27PM -0800, Mel Pilgrim wrote: > I used freebsd-update to upgrade several 11.3-p5 systems to 12.1-p1. > The etc update process added the ntpd/ntpd user/group. It showed the > line changes in the plaintext passwd/group files, but the process > appears to omit the pwd_mkdb step. > > After the upgrade, ntpd fails to start: > > # service ntpd start > Starting ntpd. > su: unknown login: ntpd > /etc/rc.d/ntpd: WARNING: failed to start ntpd > > Running the usual pwd_mkdb command fixes the issue. I've had varied results with the same thing from 11.2 to 12.1. Sometimes it works, oftentimes it does not. pwd_mkdb does fix it up, but would be nice to not have to do that. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
11.3->12.1 upgrade, pwd db not rehashed after adding ntpd user?
I used freebsd-update to upgrade several 11.3-p5 systems to 12.1-p1. The etc update process added the ntpd/ntpd user/group. It showed the line changes in the plaintext passwd/group files, but the process appears to omit the pwd_mkdb step. After the upgrade, ntpd fails to start: # service ntpd start Starting ntpd. su: unknown login: ntpd /etc/rc.d/ntpd: WARNING: failed to start ntpd Running the usual pwd_mkdb command fixes the issue. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Disabling speculative execution mitigations
On Fri, 6 Dec 2019 at 22:54, O'Connor, Daniel wrote: > > With respect to the man page, I find it difficult to know what a given value > for each sysctl will do, as evidenced by my confusion above about IBRS. scottl recently moved these sysctls to machdep.mitigations in r355436, but they've kept the existing names and sense. So, some still have an enable control while some are disable, some report "state: inactive" while others report "active: 0". Work is ongoing now to rationalize these so that the sense is true for mitigation enabled. Backwards compatibility will be maintained for the sysctl paths in stable (e.g. hw.ibrs*) but not the interim names (machdep.mitigations.*) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
