Hello,
the rpc.lockd fails to start under both 2.4.0-test1-ac19
and 2.4.0-test2 (these are the only 2.4.x kernels I have
tested). The relevant part of strace is:
execve("/sbin/rpc.lockd", ["/sbin/rpc.lockd"], [/* 62 vars */]) = 0
...
nfsservctl(0x10000, 0xbfffed58, 0) = -1 EINVAL (Invalid argument)
write(2, "lockdsvc: Invalid argument\n", 27lockdsvc: Invalid argument
) = 27
_exit(1) = ?
The 0x10000 was NFSCTL_LOCKD in 2.2 series and is actually missing
in 2.4.0, so handle_sys_nfsservctl reports EINVAL. 2.2 explicitly
redirected such call to lockdctl.
I know too little about NFS in Linux, so I do not know what is
wrong and it is very well possible that I have something
misconfigured. At least some words in Documentation/Changes
or maybe a printk-hint would be helpful.
rpc.lockd is from nfs-utils 0.1.6, NFS-related configuration is
# CONFIG_CODA_FS is not set
CONFIG_NFS_FS=m
# CONFIG_NFS_V3 is not set
CONFIG_NFSD=m
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=m
CONFIG_LOCKD=m
CONFIG_SMB_FS=m
# CONFIG_NCP_FS is not set
If you need more info, let me know.
Regards
-- Stano- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jun 26 2000 - 21:00:07 EST