From: Chuck Lever <chucklever@gmail.com>
To: Ian Kent <ikent@redhat.com>
Cc: Steve Dickson <SteveD@redhat.com>,
autofs mailing list <autofs@linux.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Libtirpc Devel List <libtirpc-devel@lists.sourceforge.net>
Subject: Re: [Libtirpc-devel] [PATCH] Autofs configure fails to detect IPv6 when libtirpc is enabled
Date: Thu, 28 Jul 2011 10:45:37 -0400 [thread overview]
Message-ID: <CAFMMQGsURY2SWv4pM5T-ofLhbVzCvC8a_+ASqJm_ZCEOXww-6g@mail.gmail.com> (raw)
In-Reply-To: <1311863605.3332.17.camel@perseus.themaw.net>
On Thu, Jul 28, 2011 at 10:33 AM, Ian Kent <ikent@redhat.com> wrote:
> On Thu, 2011-07-28 at 07:20 -0400, Chuck Lever wrote:
>> On Jul 27, 2011, at 10:26 PM, Ian Kent wrote:
>> >
>> > Umm ...
>> >
>> > Why is __rpcb_findaddr() declared in the public header files but not
>> > defined anywhere is the source?
>> >
>> > Why is __rpcb_findaddr_timed() defined in the source but not defined in
>> > the public header files?
>>
>> This version of libtirpc was split from the Sun version over a decade
>> ago when the code was immature. So you're going to find this kind of
>> thing in many places.
>
> Yes, I was aware of that, but haven't paid enough attention to the doc.
>
>>
>> The TI-RPC API is defined in 816-1435. You really shouldn't consider
>> using any of the interfaces defined in the headers but not in that
>> doc, as those are internal interfaces and can change.
>
> Ummm .. rpcb_getaddr() might be what I'm looking for, I'll look further.
>
>>
>> On the other hand, we have at least two important RPC-based
>> applications that can make use of this interface. I wonder if it
>> makes sense to harden that API but leave it hidden, so apps external
>> to the library can depend on it.
>
> Yeah, but if I can achieve what I need without it that's the way I'll
> go. It looks like I might not be able to do what I want the way I want
> with ti-rpc but it is still too early to tell. It's also too early to
> tell if ti-rpc actually already does some or all of what I need already.
> Time will tell.
>
> One example of something I need is to control the timeout, not the
> timeout for interactions after the client is constructed but the timeout
> of the client construction itself, including any queries to rpcbind that
> may be needed (hence why I want to do that manually too).
Yes, nfs-utils does this too. See support/nfs/rpc_socket.c. It looks
a lot like what is done in autofs's lib/rpc_subs.c.
--
"Blast this Christmas music! It's joyful _and_ triumphant!"
-- The Grinch
prev parent reply other threads:[~2011-07-28 14:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 12:29 [PATCH] Autofs configure fails to detect IPv6 when libtirpc is enabled Steve Dickson
2011-07-26 14:50 ` [Libtirpc-devel] " Chuck Lever
2011-07-26 21:13 ` Steve Dickson
2011-07-27 0:57 ` Ian Kent
2011-07-27 1:23 ` Ian Kent
2011-07-27 2:02 ` Ian Kent
2011-07-27 2:10 ` Chuck Lever
2011-07-27 2:09 ` Chuck Lever
2011-07-27 2:40 ` Ian Kent
2011-07-27 3:13 ` Ian Kent
2011-07-27 3:30 ` Chuck Lever
2011-07-27 3:39 ` Ian Kent
2011-07-27 6:37 ` Ian Kent
2011-07-28 2:26 ` Ian Kent
2011-07-28 11:20 ` Chuck Lever
2011-07-28 14:33 ` Ian Kent
2011-07-28 14:45 ` Chuck Lever [this message]
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=CAFMMQGsURY2SWv4pM5T-ofLhbVzCvC8a_+ASqJm_ZCEOXww-6g@mail.gmail.com \
--to=chucklever@gmail.com \
--cc=SteveD@redhat.com \
--cc=autofs@linux.kernel.org \
--cc=ikent@redhat.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).