From: Olaf Kirch <okir@suse.de>
To: nfs@lists.sourceforge.net
Subject: [PATCH 0/22] Introduction to lockd patches
Date: Sat, 5 Aug 2006 15:06:47 +0200 [thread overview]
Message-ID: <20060805130647.GA8011@suse.de> (raw)
Subject: Introduction to lockd patches
This set of patches does various cleanups in the lockd code, adds the
ability to use the client host name instead of the IP address (which
is something the HA folks asked us for), and the ability to switch
between the user space rpc.statd and a new kernel statd implementation.
The latter needs a separate user space utility named sm-notify that
sends out the NSM_NOTIFY calls at boot. The utility is available
from ftp://ftp.lst.de/pub/people/okir/sm-notify.
This code has been in several Suse releases. I forward ported this to
2.6.18-rc3 and made sure it compiles. I have *not* done any testing yet,
as I ran out of time (I'm leaving for vacation tomorrow). I wanted to
post this code for your review nevertheless, since I promised Steve
Dickson I'd do that :)
If the kernel statd code is too controversial, I'm fine with keeping
that in the suse tree a little longer. But I do believe it makes things
a lot easier for users (one configuration mistake less); and it also
makes the code simpler (no more funky upcalls to user land).
Note that both the use of hostnames instead of addresses, and the use
of kernel statd, are switchable, and default to off.
Olaf
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2006-08-05 13:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060805130647.GA8011@suse.de \
--to=okir@suse.de \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.