Messages in this thread | | | Date | Mon, 24 Jul 2000 14:46:03 +0200 (CEST) | Subject | Re: NFSCTL_LOCKD (0x10000) unimplemented? (2.4.0-test5-pre4) | From | Trond Myklebust <> |
| |
>>>>> " " == Tigran Aivazian <tigran@veritas.com> writes:
> ok, what about statd? can I leave it out of userspace startup > too (/usr/sbin/rpc.statd) or not?
Unfortunately not. The nature of lock monitoring means that rpc.statd needs to write stuff (the address of either the server on which locks are held or the clients which are holding locks) to permanent storage. It would be a very bad candidate for a kernel-space implementation.
Cheers, Trond
- 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/
| |