[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A6FDE6B975803043804A49F12F49028E0F59CC@hawk.exanet-il.co.il>
Date: Thu, 10 May 2007 13:59:57 +0300
From: "Menny Hamburger" <menny@...net.com>
To: "Neil Brown" <neilb@...e.de>
Cc: <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] NLM program ID for user space NLM server
Hi,
We have a our own userland NFSD and NLM service running that implement
all the NLM/NFS functionality.
We do not want to modify the way the client does his mounts.
M.
-----Original Message-----
From: Neil Brown [mailto:neilb@...e.de]
Sent: Thursday, May 10, 2007 12:03 PM
To: Menny Hamburger
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] NLM program ID for user space NLM server
On Thursday May 10, menny@...net.com wrote:
> Hi,
>
> Since the current kernel cannot be compiled with NFS client and
> without lockd, it is not possible to register a user space NLM server
> Without colliding with the kernel service registered in
> .../fs/lockd/lockd.c.
This doesn't make any sense to me at all.
You can certainly have the NFS client compiled and even running without
lockd running (if you mount with "-o nolock") and in that case you are
free you register your owner user-space NLM server (though I'm not sure
what good it would do you).
And if you want to mount an NFS filesystem without "-o nolock", then you
really need the kernel lockd running, or locking will not work.
Can you explain what you are trying to do - I'm curious.
>
> +#ifndef
> #define NLM_PROGRAM 100021
> +#endif
Uhm... Do you mean
+#ifndef NLM_PROGRAM
?? Still not sure how that helps.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists