From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Jeff Layton <jlayton@redhat.com>
Cc: NFSv3 list <linux-nfs@vger.kernel.org>, nfsv4@linux-nfs.org
Subject: Re: ANNOUNCE: nfs-utils-1.2.2 released.
Date: Mon, 8 Mar 2010 13:11:17 +0100 [thread overview]
Message-ID: <20100308121117.GW19154@ics.muni.cz> (raw)
In-Reply-To: <20100308070209.7cabb55f@tlielax.poochiereds.net>
On Mon, Mar 08, 2010 at 07:02:09AM -0500, Jeff Layton wrote:
> (cc'ing Olga)
> =
> Hmm....gssd in 1.2.2 seems to work fine for me. The only changes in
> that area of the code were some of Olga's patches that went into 1.2.2.
> Olga, any thoughts?
It does not work for me and for one student that works on some patches.
We both have an issue with compilation as well as I mentioned earlier.
> Lukas, could you also tell us what kernel you're using, and maybe send
> the output of ldd against the binary?
My kernel is 2.6.33. The student's kernel is about 2.6.31 or 2.6.32.
ldd /tmp/nfs-utils-1.2.2/utils/gssd/gssd
linux-vdso.so.1 =3D> (0x00007fff317ed000)
libgssapi_krb5.so.2 =3D> /usr/lib/libgssapi_krb5.so.2 (0x00007faa7c=
631000)
libkrb5.so.3 =3D> /usr/lib/libkrb5.so.3 (0x00007faa7c36d000)
libk5crypto.so.3 =3D> /usr/lib/libk5crypto.so.3 (0x00007faa7c146000)
libcom_err.so.2 =3D> /lib/libcom_err.so.2 (0x00007faa7bf42000)
librpcsecgss.so.3 =3D> /usr/lib/librpcsecgss.so.3 (0x00007faa7bd320=
00)
libgssglue.so.1 =3D> /usr/lib/libgssglue.so.1 (0x00007faa7bb27000)
libdl.so.2 =3D> /lib/libdl.so.2 (0x00007faa7b923000)
libc.so.6 =3D> /lib/libc.so.6 (0x00007faa7b5a2000)
libkrb5support.so.0 =3D> /usr/lib/libkrb5support.so.0 (0x00007faa7b=
399000)
libkeyutils.so.1 =3D> /lib/libkeyutils.so.1 (0x00007faa7b196000)
libresolv.so.2 =3D> /lib/libresolv.so.2 (0x00007faa7af7d000)
libpthread.so.0 =3D> /lib/libpthread.so.0 (0x00007faa7ad5f000)
/lib64/ld-linux-x86-64.so.2 (0x00007faa7c886000)
The student uses Debian, I use Ubuntu (so similar distros).
Package version
----------------------------------------------
libgssapi-krb5-2 1.8+dfsg~alpha1-7
libkrb5-3 1.8+dfsg~alpha1-7
libk5crypto3 1.8+dfsg~alpha1-7
libcomerr2 1.41.10-1ubuntu2
librpcsecgss3 0.19-2
libgssglue1 0.1-4
libc6 2.11.1-0ubuntu4
libkrb5support0 1.8+dfsg~alpha1-7
libkeyutils1 1.2-12
-- =
Luk=E1=B9 Hejtm=E1nek
next prev parent reply other threads:[~2010-03-08 12:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 14:27 ANNOUNCE: nfs-utils-1.2.2 released Steve Dickson
[not found] ` <20100304201941.GL19154@ics.muni.cz>
[not found] ` <4B9021EF.60309@oracle.com>
[not found] ` <20100304212149.GM19154@ics.muni.cz>
2010-03-04 22:30 ` Chuck Lever
2010-03-04 22:40 ` Lukas Hejtmanek
2010-03-08 10:16 ` Lukas Hejtmanek
2010-03-08 12:02 ` Jeff Layton
2010-03-08 12:11 ` Lukas Hejtmanek [this message]
2010-03-08 13:44 ` Kevin Coffman
2010-03-08 15:30 ` Lukas Hejtmanek
2010-03-08 19:21 ` Kevin Coffman
2010-03-08 19:40 ` Lukas Hejtmanek
2010-03-08 19:48 ` Jeff Layton
[not found] ` <20100308144825.0e1afa59-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-03-09 10:35 ` Lukas Hejtmanek
2010-03-09 15:18 ` Kevin Coffman
2010-03-09 15:53 ` Lukas Hejtmanek
2010-03-09 17:04 ` Kevin Coffman
2010-03-09 17:29 ` Lukas Hejtmanek
2010-03-09 17:41 ` Lukas Hejtmanek
2010-03-09 18:26 ` Kevin Coffman
2010-03-09 18:52 ` Lukas Hejtmanek
2010-03-08 19:48 ` Kevin Coffman
2010-03-08 17:42 ` Steve Dickson
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=20100308121117.GW19154@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
/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