> > Bill Davidsen wrote: > I get messages indicating "NFS statd failed" and messsages says it can't > register. Is this caused by the dbus "fix" or ??? > /quote] > > Last night, after updating for the first time in awhile (because of the dbus issues), I had this exact same problemm as Bill. I upgraded from kernel 2.6.27.5-41.fc9.x86_64 to 2.6.27.7-53.fc9.x86_64. > > I get the message "Starting NFS statd: [Failed] from the Fedora splash screen during boot up. It automatically switches to the "Show Details" option just in time to display the NFS error message. > > I rebooted to the old kernel, and, as expected, no error message appeared. Then, I rebooted to the old kernel again, but this time I manually selected "Show Details." I was surprised to see the NFS error message! > > In other words, the old kernel was also failing to get NFS started, but the error message was surpressed, and ignorance was bliss! > > It seems to me that there are 3 possible explanations: > > 1. The NFS problem had been there for who knows how long, but the update I made last night forced the error messages to be displayed during boot up. > 2. The updated kernel somehow broke NFS in the old kernel. I'm not a developer, but this seems unlikely although possible. > 3. Some other non-kernel part of the updates generally broke NFS across the board. > > Any ideas? -- This is an email sent via The Fedora Community Portal https://fcp.surfsite.org https://fcp.surfsite.org/modules/newbb/viewtopic.php?post_id=311650&topic_id=65349&forum=10#forumpost311650 If you think, this is spam, please report this to webmaster@xxxxxxxxxxxxxxxx and/or blame parminides@xxxxxxxxxxxx -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
