From: Ingo Lantschner <ingo.lists@vum.at>
To: nfs@lists.sourceforge.net
Subject: SOLVED: udp port sunrpc unreachable
Date: Thu, 02 Feb 2006 19:25:27 +0100 [thread overview]
Message-ID: <drtiqn$205$1@sea.gmane.org> (raw)
In-Reply-To: <1138894614.8894.13.camel@lade.trondhjem.org>
Hi all!
Thanks for your help - you hit the nail!! After comenting the obvious
(and only) line in /etc/default/portmap anything went fine.
Trond Myklebust wrote:
>>>>I think that's actually the debian default setting these days; with the
>>>>debconf verbosity at the default, it should have asked you about this
>>>>when portmap was installed. Just edit /etc/default/portmap to comment
>>>>out the obvious line.
>>>
>>>If true, then that would appear to be a rather ridiculous default. Have
>>>they put out a rationale for this?
>>
>>Nope, I'm wrong, the default is the opposite. So probably someone chose the
>>more secure-sounding option at install time and then forgot about it....
No, it IS the default - I have never been asked (installed with apt-get
install portmap). I use ubuntu Hoary.
May be, because it targets the desktop-user the default is only loopback.
Anyway, now its fine, thanks again to all who answered and helped.
Regards, Ingo.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-02-02 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 9:21 udp port sunrpc unreachable Ingo Lantschner
2006-02-02 14:31 ` Trond Myklebust
2006-02-02 15:19 ` J. Bruce Fields
2006-02-02 15:25 ` Trond Myklebust
2006-02-02 15:29 ` J. Bruce Fields
2006-02-02 15:36 ` Trond Myklebust
2006-02-02 18:25 ` Ingo Lantschner [this message]
2006-02-03 15:53 ` SOLVED: " Ingo Lantschner
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='drtiqn$205$1@sea.gmane.org' \
--to=ingo.lists@vum.at \
--cc=nfs@lists.sourceforge.net \
/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.