From: Jim Davis <jdavis@CS.Arizona.EDU>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: rpc.gssd segfault on FC5 client
Date: Mon, 29 Jan 2007 15:06:49 -0700 [thread overview]
Message-ID: <45BE6FF9.6000101@CS.Arizona.EDU> (raw)
In-Reply-To: <4d569c330701291402pa6760c4mf64cbfd82cfc6fd2@mail.gmail.com>
Kevin Coffman wrote:
>
> I assume you have all the pre-reqs or it wouldn't start. Just poking
> around. What do the following show?
> "rpm -qa | grep nfs"
> "rpm -qa | grep krb"
>
> What are the contents of /etc/gssapi_mech.conf?
angora$ rpm -qa | grep nfs
nfs-utils-1.0.8-4.fc5
nfs-utils-lib-1.0.8-4.FC5
system-config-nfs-1.3.19-1
nfs-utils-debuginfo-1.0.8.rc2-4.FC5.2
angora$ rpm -qa | grep krb
krb5-devel-1.4.3-5.3
krbafs-devel-1.2.2-9.2.1
krb5-server-1.4.3-5.3
krb5-workstation-1.4.3-5.3
krbafs-1.2.2-9.2.1
krb5-auth-dialog-0.6.cvs20060212-1.1
krb5-libs-1.4.3-5.3
pam_krb5-2.2.6-2.2
krbafs-utils-1.2.2-9.2.1
angora$ cat /etc/gssapi_mech.conf
# Example /etc/gssapi_mech.conf file
#
# GSSAPI Mechanism Definitions
#
# This configuration file determines which GSS-API mechanisms
# the gssd code should use
#
# NOTE:
# The initiaiization function "mechglue_internal_krb5_init"
# is used for the MIT krb5 gssapi mechanism. This special
# function name indicates that an internal function should
# be used to determine the entry points for the MIT gssapi
# mechanism funtions.
#
# library initialization function
# ================================ ==========================
# The MIT K5 gssapi library, use special function for initialization.
libgssapi_krb5.so.2 mechglue_internal_krb5_init
#
# The SPKM3 gssapi library function. Use the function spkm3_gss_initialize.
# /usr/local/gss_mechs/spkm/spkm3/libgssapi_spkm3.so spkm3_gss_initialize
-------------------------------------------------------------------------
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-29 22:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 15:20 question about fh_copy Ming Zhang
2007-01-28 23:01 ` J. Bruce Fields
2007-01-29 0:36 ` Ming Zhang
2007-01-29 1:04 ` J. Bruce Fields
2007-01-29 14:10 ` Ming Zhang
2007-01-29 20:35 ` rpc.gssd segfault on FC5 client Jim Davis
2007-01-29 22:02 ` Kevin Coffman
2007-01-29 22:06 ` Jim Davis [this message]
2007-01-29 22:44 ` Kevin Coffman
2007-01-29 22:49 ` Jim Davis
2007-01-29 23:18 ` Kevin Coffman
2007-01-29 23:34 ` Jim Davis
2007-01-30 0:02 ` Kevin Coffman
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=45BE6FF9.6000101@CS.Arizona.EDU \
--to=jdavis@cs.arizona.edu \
--cc=kwc@citi.umich.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox