From: Steve Dickson <SteveD@redhat.com>
To: james bardin <jbardin@bu.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs sec=krb5 on RHEL and CentOS
Date: Wed, 24 Jan 2007 06:05:55 -0500 [thread overview]
Message-ID: <45B73D93.1020508@RedHat.com> (raw)
In-Reply-To: <a3b675320701211411r45d010f8jd7132deedcf68804@mail.gmail.com>
Sorry for the delayed response...
james bardin wrote:
> I couldn't get sec=krb5 to work on clients running RHEL4 (and CentOS),
> so I built a slightly newer version of nfs-utils. (nfs-utils-1.0.7-13)
Go back and grab the latest rhel4 nfs-utils which is 1.0.6-77. That has
been updated with a number of patches that are in the upstream
version...
>
> A mkdir return a file exists error, but the directory is created.
> Redirecting std out to a file returns an ioerror, and the file is
> created but empty.
> Vim creates swap files, they fail so it doesn't use them, but reports
> them as existing.
>
> I can chmod, chown existing files as expected.
hmm... if this continues after you updated your nfs-utils, please
open a bug reported and post a bzip2 binary tethereal trace
something similar to:
tethereal -w /tmp/data.pcap host <server> ; bzip2 /tmp/data.pcap
steved.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-01-24 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 22:11 nfs sec=krb5 on RHEL and CentOS james bardin
2007-01-24 11:05 ` Steve Dickson [this message]
2007-01-24 15:03 ` James Bardin
2007-01-24 20:58 ` James Bardin
2007-01-24 23:39 ` J. Bruce Fields
2007-01-25 0:14 ` james bardin
2007-01-25 19:43 ` James Bardin
2007-01-25 21:56 ` James Bardin
2007-01-25 23:14 ` Kevin Coffman
2007-01-25 23:40 ` James Bardin
2007-01-26 17:07 ` James Bardin
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=45B73D93.1020508@RedHat.com \
--to=steved@redhat.com \
--cc=jbardin@bu.edu \
--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.