Date: Sun, 13 Feb 2022 22:05:32 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 261939] Kerberized NFS mount requires the gssd to be restarted Message-ID: <bug-261939-227-VJDCvho57z@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261939-227@https.bugs.freebsd.org/bugzilla/> References: <bug-261939-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261939 --- Comment #1 from Rick Macklem <rmacklem@FreeBSD.org> --- Created attachment 231803 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D231803&action= =3Dedit Modify rc.d/gssd so that daemon starts after NETWORKING, kdc Arno Tuber reported via email that he had to restart the gssd daemon after booting, to get a Kerberized NFS mount to work. When I did an rcorder in /etc/rc.d, I noticed that the gssd would start before NETWORKING and the kdc. The latter would only matter if the KDC is on the same machine, but the gssd will need to use NETWORKING to communicate with the KDC. This patch adds NETWORKING and kdc to the REQUIRE line in /etc/rc.d/gssd so that the daemon starts later. Hopefully Arno will be able to test this and report if it fixes the problem for him? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261939-227-VJDCvho57z>