Bug 7176
Summary: | rpc.lockd doesn't start | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | pzz |
Component: | nfs-utils | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | kie, shannon_hill, ung |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-08-09 02:33:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
pzz
1999-11-20 13:00:25 UTC
Are you using RedHat's kernel, or a custom kernel? If custom, I'd bet it's missing the compile-time support for kernel-nfs. Only if the option "Prompt for development drivers" is checked under "Code maturity options", then you'll be able to enable the "NFS server support" option under "Network File Systems". I use the custom kernel (2.2.13) but I've turned on "Prompt for development drivers" as well as "NFS server support". I have this same exact problem when trying to build/run the 2.2.13 kernel with rh6.1 I have "Prompt for development drivers" ON. I've tried both built-in and modular nfs server support. "Work like SUN" I've always left ON. Still, when I try to invoke rpc.lockd, it fails with "Invalid Argument". Does the stock rh6.1 kernel (2.2.12-20) have patches applied to it that are not in the main line of kernel development? Why does rpc.lockd work fine with 2.2.12-20 and fail with 2.2.13? assigned to johnsonm This is not a problem with newer NFS code; the kernel will start lockd automatically when needed (in fact, the rawhide nfs-utils init script only starts statd.) |