From: Chuck Lever <chuck.lever@oracle.com>
To: Steven Shiau <steven@nchc.org.tw>
Cc: Ben Hutchings <ben@decadent.org.uk>,
579397@bugs.debian.org, linux-nfs@vger.kernel.org
Subject: Re: Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254
Date: Tue, 06 Jul 2010 13:05:17 -0400 [thread overview]
Message-ID: <4C33624D.2070405@oracle.com> (raw)
In-Reply-To: <4C0FA7FD.3000301@nchc.org.tw>
On 06/ 9/10 10:41 AM, Steven Shiau wrote:
>
>
> On 2010=E5=B9=B406=E6=9C=8806=E6=97=A5 04:29, Ben Hutchings wrote:
>> On Thu, 2010-06-03 at 17:08 -0400, Chuck Lever wrote:
>>> On 05/24/10 11:22 AM, Chuck Lever wrote:
>> [...]
>>>> We can probably remove the reverse mapping constraint for presenta=
tion
>>>> addresses. A simple fix might be to change statd_canonical_name() =
from:
>>>>
>>>> freeaddrinfo(ai);
>>>> if (!result)
>>>> return NULL;
>>>>
>>>> to
>>>>
>>>> freeaddrinfo(ai);
>>>> if (!result)
>>>> return strdup(hostname);
>>>>
>>>> Let me know if this works.
>>> Any update? I have a patch ready for nfs-utils to fix this regressi=
on,
>>> but I need confirmation that it addresses your problem.
>> Steven originally had this problem, not me. Steven, do you need me t=
o
>> build a new package with this change?
>>
>> Ben.
>>
> Ben,
> Yes, please.
> Thanks.
Any progress on this?
next prev parent reply other threads:[~2010-07-06 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BF71C27.7070309@nchc.org.tw>
2010-05-22 1:38 ` Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254 Ben Hutchings
2010-05-24 15:22 ` Chuck Lever
2010-06-03 21:08 ` Chuck Lever
2010-06-05 20:29 ` Ben Hutchings
2010-06-09 14:41 ` Steven Shiau
2010-07-06 17:05 ` Chuck Lever [this message]
2010-08-08 4:59 ` Ben Hutchings
2010-08-08 16:55 ` 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=4C33624D.2070405@oracle.com \
--to=chuck.lever@oracle.com \
--cc=579397@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=linux-nfs@vger.kernel.org \
--cc=steven@nchc.org.tw \
/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.