Linux NFS development
 help / color / mirror / Atom feed
From: "Aníbal Monsalve Salazar" <anibal@debian.org>
To: linux-nfs@vger.kernel.org
Cc: Richard A Nelson <cowboy@debian.org>, 484861@bugs.debian.org
Subject: Bug#484861: nfs-common: rpc.statd --outgoing-port (-o) option broken
Date: Sun, 5 Oct 2008 15:51:33 +1100	[thread overview]
Message-ID: <20081005045133.GZ26991@debianrules.debiancolombia.org> (raw)
In-Reply-To: <20080607015302.15770.62792.reportbug@gothic-ave.svl.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2336 bytes --]

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 
>rpc.statd  4136       statd    7u     IPv4      10396 UDP *:32765 
>rpc.statd  4136       statd    8u     IPv4      10399 TCP *:32765 (LISTEN)
>
>changing --outgoing-port to -o didn't help.
>
>This is causing issues with my firewalls

Is this a known bug in 1.1.2?

>-- System Information:
>Debian Release: 4.0
>  APT prefers testing-proposed-updates
>  APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable')
>Architecture: i386 (i686)
>
>Kernel: Linux 2.6.25.3 (SMP w/2 CPU cores)
>Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
>Shell: /bin/sh linked to /bin/bash
>
>Versions of packages nfs-common depends on:
>ii  adduser                     3.108        add and remove users and groups
>ii  initscripts                 2.86.ds1-59  Scripts for initializing and shutt
>ii  libc6                       2.7-12       GNU C Library: Shared libraries
>ii  libcomerr2                  1.40.8-2     common error description library
>ii  libevent1                   1.3e-3       An asynchronous event notification
>ii  libgssglue1                 0.1-2        mechanism-switch gssapi library
>ii  libkrb53                    1.6.dfsg.3-2 MIT Kerberos runtime libraries
>ii  libnfsidmap2                0.20-1       An nfs idmapping library
>ii  librpcsecgss3               0.18-1       allows secure rpc communication us
>ii  libwrap0                    7.6.q-15     Wietse Venema's TCP wrappers libra
>ii  lsb-base                    3.2-12       Linux Standard Base 3.2 init scrip
>ii  netbase                     4.32         Basic TCP/IP networking system
>ii  portmap                     6.0-5.1      RPC port mapper
>ii  ucf                         3.007        Update Configuration File: preserv
>
>nfs-common recommends no packages.
>
>-- no debconf information

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

       reply	other threads:[~2008-10-05  4:51 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 ` Aníbal Monsalve Salazar [this message]
     [not found]   ` <20081005045133.GZ26991-ePWG1nzy00eujY+JMLXK6WCv5UukjcD9wsqeKsqY1Ps@public.gmane.org>
2008-10-08 12:47     ` Bug#484861: nfs-common: rpc.statd --outgoing-port (-o) option broken Steve Dickson

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=20081005045133.GZ26991@debianrules.debiancolombia.org \
    --to=anibal@debian.org \
    --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