Bug 7176 - rpc.lockd doesn't start
rpc.lockd doesn't start
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils (Show other bugs)
7.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-20 08:00 EST by pzz
Modified: 2008-05-01 11:37 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-08 22:33:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description pzz 1999-11-20 08:00:25 EST
rpc.lockd fails to start. On startup it prints the message
    lockdsvc: Invalid argument
and dies.
Comment 1 Rex Dieter 1999-12-03 16:39:59 EST
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".
Comment 2 pzz 1999-12-04 17:29:59 EST
I use the custom kernel (2.2.13) but I've turned on "Prompt for development
drivers" as well as "NFS server support".
Comment 3 Shannon Hill 2000-01-05 10:20:59 EST
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?
Comment 4 Cristian Gafton 2000-08-08 22:33:52 EDT
assigned to johnsonm
Comment 5 Bill Nottingham 2001-03-07 23:30:35 EST
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.)

Note You need to log in before you can comment on or make changes to this bug.