[OpenAFS] Re: PAG lost after switching users on Slackware 13.1 box

[Tom Mukunnemkeril]

=0A=0A--- On Mon, 1/24/11, Andrew Deason <adeason@sinenomine.net> wrote:=0A=
=0A> From: Andrew Deason <adeason@sinenomine.net>=0A> Subject: [OpenAFS] Re=
: PAG lost after switching users on Slackware 13.1 box=0A> To: openafs-info=
@openafs.org=0A> Date: Monday, January 24, 2011, 4:35 PM=0A> On Fri, 21 Jan=
 2011 17:30:57 -0600=0A> Andrew Deason <adeason@sinenomine.net>=0A> wrote:=
=0A> =0A> > On Fri, 21 Jan 2011 14:42:26 -0800 (PST)=0A> > Tom Mukunnemkeri=
l <torrent_tech@yahoo.com>=0A> wrote:=0A> > =0A> > > id shows a value, but =
/proc/keys does not.=A0=0A> In the Slackware 13.0=0A> > > installation, /pr=
oc/keys does show a value after=0A> I execute pagsh.=0A> > =0A> > Hm, so I =
wonder if either keyrings are not working, or=0A> we think you=0A> > don't =
have them. If you have the 'configure' output or=0A> the config.log=0A> > f=
rom when you compiled the kernel module, what does it=0A> say about linux=
=0A> > kernel keyring support, and the surrounding messages?=0A> =0A> For p=
osterity, this issue apparently went away when the=0A> OpenAFS client=0A> w=
as recompiled. My guess is that it was something with the=0A> configure=0A>=
 tests, but who knows.=0A=0AOops, I sent the email to just Andrew.  Looking=
 at my notes from the past few months, I probably recompiled AFS, then reco=
mpiled the kernel for keyring support, but  probably didn't recompile AFS b=
ased on the new kernel.=0A=0AI'm happy to report all is working now.  My we=
bserver is able to access files in AFS space.  I'm even upgraded to kernel =
2.6.37 and Openafs-1.4.14 now.  =0A=0AThanks again for all your help.=0A=0A=
Tom=0A=0A=0A