From: "G. Allen Morris III" <gam3@gam3.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nhorman@redhat.com, nfs@lists.sourceforge.net
Subject: statd -o change
Date: Fri, 4 Mar 2005 10:34:36 -0500 [thread overview]
Message-ID: <20050304153436.GA32203@gam3.net> (raw)
In-Reply-To: <1109787034.12460.7.camel@lade.trondhjem.org>
Trond,
I would think that statd should fail if the requested outgoing port (-o)
can't be bound to. The main reason to bind to a particular outgoing port
is because of a firewall. If a random port is used statd will not make
it through the firewall, but the log file will have to be checked to
find out why statd is not working (falling back on randomly chosen port).
Not starting statd seems to be the failure mode if the rpc.statd port
(-p) can't be bound to.
Allen <gam3@gam3.net>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-03-04 15:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 19:21 [RFC] implementing BSD style locks on NLM (flocks) nhorman
2005-03-02 15:56 ` Olaf Kirch
2005-03-02 18:10 ` Trond Myklebust
2005-03-02 18:44 ` Olaf Kirch
2005-03-02 18:55 ` Trond Myklebust
2005-03-03 18:24 ` nhorman
2005-03-03 21:19 ` Trond Myklebust
2005-03-14 15:29 ` Trond Myklebust
2005-03-04 15:02 ` statd -o change G. Allen Morris III
2005-03-04 15:34 ` G. Allen Morris III [this message]
2005-03-04 19:48 ` Trond Myklebust
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=20050304153436.GA32203@gam3.net \
--to=gam3@gam3.net \
--cc=nfs@lists.sourceforge.net \
--cc=nhorman@redhat.com \
--cc=trond.myklebust@fys.uio.no \
/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.