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

Tom Mukunnemkeril torrent_tech@yahoo.com
Fri, 21 Jan 2011 14:42:26 -0800 (PST)

=0A--- On Fri, 1/21/11, Andrew Deason <adeason@sinenomine.net> wrote:=0A=0A=
> From: Andrew Deason <adeason@sinenomine.net>=0A> Subject: [OpenAFS] Re: P=
AG lost after switching users on Slackware 13.1 box=0A> To: openafs-info@op=
enafs.org=0A> Date: Friday, January 21, 2011, 3:53 PM=0A> On Thu, 20 Jan 20=
11 18:17:00 -0800=0A> (PST)=0A> Tom Mukunnemkeril <torrent_tech@yahoo.com>=
=0A> wrote:=0A> =0A> > Is there anything I can do to debug this further to=
=0A> figure out why the=0A> > PAG is getting lost?=A0 The version of glibc =
is=0A> different, and I don't=0A> > know if this would cause a problem, or =
is there=0A> something I need to=0A> > enable in the kernel.=0A> =0A> You c=
an look at what what is happening to your PAG, which=0A> can be=0A> identif=
ied by the output of 'id -a' and/or 'keyctl show'.=0A> Try running=0A> thes=
e once you obtain a PAG and after you lose it. At first=0A> you should=0A> =
see something like:=0A> =0A> # id -a=0A> uid=3D0(root) gid=3D0(root) groups=
=3D0(root),1107203568=0A> =0A> and=0A> =0A> # keyctl show=0A> Session Keyri=
ng=0A> =A0 =A0 =A0=A0=A0-3 --alswrv=A0 =A0=0A> =A0 0=A0 =A0=A0=A00=A0 keyri=
ng:=0A> _ses.21944=0A> 271956261 ----s--v=A0 =A0 =A0 0=A0=0A> =A0=A0=A00=A0=
=A0=A0\_ afs_pag: _pag=0A> =0A> The last big group in the 'id' output, and =
the afs_pag key=0A> in your=0A> session keyring can be used to identify you=
r PAG. After you=0A> su, I'd=0A> expect both of them to be gone. Is that th=
e case?=0A> =0A=0Aid shows a value, but /proc/keys does not.  In the Slackw=
are 13.0 installation, /proc/keys does show a value after I execute pagsh.=
=0A=0A=0Abash-4.1# pagsh=0Ash-4.1# id=0Auid=3D0(root) gid=3D0(root) groups=
-4.1# cat /proc/keys=0Ash-4.1# =0A=0A=0A=0A> It may have something to do wi=
th how much su sanitizes the=0A> environment,=0A> but I'm not sure.=0A> =0A=
> > Both Slackware distributions run Openafs- and=0A> Kernel=0A> > => =0A> You may want to use OpenAFS 1.4.14. There's at least one=
=0A> change in there=0A> for 2.6.35, though it shouldn't be affecting this.=
=0A> =0A> -- =0A=0AI will try to upgrade OpenAFS 1.4.14 but have doubts thi=
s will help since my Slackware 13.0 installation with linux and Op=
enAFS- seems to work fine.=0A=0A=0ATom=0A=0A=0A