public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: linux-nfs@vger.kernel.org
Cc: nfsv4@linux-nfs.org, Steve Dickson <SteveD@redhat.com>
Subject: [PATCH 0/2] Make libtirpc work with old style portmapper
Date: Mon, 30 Aug 2010 15:03:19 +0200	[thread overview]
Message-ID: <201008301503.19783.okir@suse.de> (raw)


Hi Steve et al,

We recently got a bug report from a customer trying to run nfs-utils
(which is compiled against libtirpc on SLES 11) on a system with
portmapper installed instead of rpcbind. Which failed miserably,
because none of the RPC servers was able to register with portmap.

One might argue, if it hurts don't do it, but OTOH this configuration
isn't totally outlandish. In particular, ISVs may decide they want
to compile an RPC enabled application against libtirpc, but still
want it to run on a wide range of Linux versions.

I looked into the issue and put together the following two patches,
which I'm submitting for your kindly review.

Thanks
Olaf
-- 
Neo didn't bring down the Matrix. SOA did. (soafacts.com)
--------------------------------------------
Olaf Kirch - Director Server (okir@novell.com)
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

             reply	other threads:[~2010-08-30 13:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 13:03 Olaf Kirch [this message]
2010-08-30 13:04 ` [PATCH 1/2] Introduce new helper function getpmaphandle Olaf Kirch
2010-08-30 13:04   ` [PATCH 2/2] " Olaf Kirch
2010-08-30 15:59 ` [PATCH 0/2] Make libtirpc work with old style portmapper Chuck Lever
2010-08-30 16:19   ` Olaf Kirch
2010-08-30 23:48     ` Chuck Lever
2010-09-07 11:27       ` Olaf Kirch
2010-09-07 15:36         ` Chuck Lever
2010-09-07 20:58           ` Olaf Kirch
2010-09-07 21:15             ` Chuck Lever

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=201008301503.19783.okir@suse.de \
    --to=okir@suse.de \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox