From: "Brandon D. Valentine" <brandon@dvalentine.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: [bug] FC2/2.6.8.1 does not fallback to NFSv2
Date: Sat, 28 Aug 2004 13:38:47 -0500 [thread overview]
Message-ID: <20040828183847.GA84014@brandon.dvalentine.com> (raw)
In-Reply-To: <4130BC76.9070202@RedHat.com>
On Sat, Aug 28, 2004 at 01:10:14PM -0400, Steve Dickson wrote:
> Upgrade your nfs-utils to the latest rawhide version
> (nfs-utils-1.0.6-31 I believe) to see if it take care of the problem.
> I think this has to do with the order of how mountd and rpc.imapd are
> started. Basically mountd has to be running before rpc.idmapd for
> things to work... So in the case of the server (where rpc.idmapd is
> already started), the nfs startup script send rpc.idmapd a signal
> telling it to reopen its nfsd files (i.e. files under /proc/fs/nfsd )
I do not see how rpc.idmapd has anything at all to do with NFSv2/3, it
is an NFSv4ism. Also, rpc.mountd on the server is working fine, as
evidenced by the rpcinfo output I included in a previous message and the
fact that every other client on the network mounts filesystems from it
successfully.
In other words: what the heck are you talking about? =)
Brandon D. Valentine
--
brandon@dvalentine.com http://www.geekpunk.net
Pseudo-Random Googlism: sunshine is a great game that anyone will enjoy
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-08-28 18:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 21:22 [bug] FC2/2.6.8.1 does not fallback to NFSv2 Brandon D. Valentine
2004-08-27 21:36 ` Trond Myklebust
2004-08-27 21:51 ` Trond Myklebust
2004-08-27 23:32 ` Brandon D. Valentine
2004-08-27 23:34 ` Brandon D. Valentine
2004-08-28 5:35 ` Trond Myklebust
2004-08-28 6:29 ` Brandon D. Valentine
2004-08-28 18:45 ` Trond Myklebust
2004-08-28 19:57 ` Brandon D. Valentine
2004-08-28 20:31 ` James Pearson
2004-08-28 17:10 ` Steve Dickson
2004-08-28 18:38 ` Brandon D. Valentine [this message]
2004-08-29 1:32 ` Steve Dickson
2004-08-29 2:13 ` Brandon D. Valentine
2004-08-28 9:32 ` raven
2004-08-28 16:47 ` James Pearson
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=20040828183847.GA84014@brandon.dvalentine.com \
--to=brandon@dvalentine.com \
--cc=SteveD@redhat.com \
--cc=nfs@lists.sourceforge.net \
--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.