From: Steve Dickson <SteveD@redhat.com>
To: linux-nfs@vger.kernel.org, Richard A Nelson <cowboy@debian.org>,
484861@bugs.debian.org
Subject: Re: Bug#484861: nfs-common: rpc.statd --outgoing-port (-o) option broken
Date: Wed, 08 Oct 2008 08:47:50 -0400 [thread overview]
Message-ID: <48ECABF6.40107@RedHat.com> (raw)
In-Reply-To: <20081005045133.GZ26991-ePWG1nzy00eujY+JMLXK6WCv5UukjcD9wsqeKsqY1Ps@public.gmane.org>
An=EDbal Monsalve Salazar wrote:
> On Sat, Jun 07, 2008 at 01:53:02AM +0000, Richard A Nelson wrote:
>> Package: nfs-common
>> Version: 1:1.1.2-4
>> Severity: important
>>
>> In a fit of debugging spurious NFS problems I noticed this:
>>
>> # ps auxw | grep statd
>> statd 4136 0.0 0.0 2056 652 ? Ss Jun06 0:00
>> /sbin/rpc.statd --port 32765 --outgoing-port 32766
>>
>> # lsof | grep rpc.statd | grep :
>> rpc.statd 4136 statd 5u IPv4 10388 UDP *:920=20
>> rpc.statd 4136 statd 7u IPv4 10396 UDP *:32765=20
>> rpc.statd 4136 statd 8u IPv4 10399 TCP *:32765 (L=
ISTEN)
>>
>> changing --outgoing-port to -o didn't help.
>>
>> This is causing issues with my firewalls
>=20
> Is this a known bug in 1.1.2?
No...=20
Please file a bug report at https://bugzilla.linux-nfs.org
steved.
prev parent reply other threads:[~2008-10-08 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080607015302.15770.62792.reportbug@gothic-ave.svl.ibm.com>
2008-10-05 4:51 ` Bug#484861: nfs-common: rpc.statd --outgoing-port (-o) option broken Aníbal Monsalve Salazar
[not found] ` <20081005045133.GZ26991-ePWG1nzy00eujY+JMLXK6WCv5UukjcD9wsqeKsqY1Ps@public.gmane.org>
2008-10-08 12:47 ` Steve Dickson [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=48ECABF6.40107@RedHat.com \
--to=steved@redhat.com \
--cc=484861@bugs.debian.org \
--cc=cowboy@debian.org \
--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