[OpenAFS] OpenAFS + Linux +XP
Eggert, Richard W, II (Rich), GVSOL
rweggert@att.com
Thu, 22 Jan 2004 13:29:49 -0600
This is a multi-part message in MIME format.
------_=_NextPart_001_01C3E11E.19D4448F
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Okay, so how does one fix it?
=20
Rich
-----Original Message-----
From: Jeffrey Altman [mailto:jaltman@columbia.edu]
Sent: Thursday, January 22, 2004 2:23 PM
To: Eggert, Richard W, II (Rich), GVSOL
Cc: openafs-info@openafs.org
Subject: Re: [OpenAFS] OpenAFS + Linux +XP
In this scenario, if you are not using the MS Loopback Adapter
then the OpenAFS client service is going to crash as soon as it
detects the network has failed. If this happens while Integrated
Logon is being executed and attempting to SetToken bad bad bad
things could easily be seen happening.
Jeffrey Altman
Eggert, Richard W, II (Rich), GVSOL wrote:
If I recall correctly, I ran into the blue screens most often on my
laptop (which runs XP PRo). If I left it idle while holding AFS tokens,
the laptop would go back into standby mode, which would wipe out any
network connections. When trying to start back up, it seemed to want to
log back in, something would go wrong (probably due to the wireless
network interface not coming back up right away), and I'd get a blue
screen of death.
My memory is a bit foggy, but this is how I remember it happening.
Rich=20
-----Original Message-----
From: ted creedon [ mailto:tcreedon@easystreet.com]
Sent: Thursday, January 22, 2004 1:36 PM
To: openafs-info@openafs.org
Subject: RE: [OpenAFS] OpenAFS + Linux +XP
Yes but he did compile it himself which often corrects whatever..
Rodney's work provides a painless way to preserve user information on a
redundant file system. It also solves the SSO problem on mixed systems.
As stated before, when BOTH AD servers crash (multiple power outages)
you're
in trouble.
tedc
-----Original Message-----
From: openafs-info-admin@openafs.org
[ mailto:openafs-info-admin@openafs.org]
On Behalf Of Rodney M Dyer
Sent: Thursday, January 22, 2004 10:20 AM
To: openafs-info@openafs.org
Subject: Re: [OpenAFS] OpenAFS + Linux +XP
At 01:00 PM 1/22/2004, Jeffrey Altman wrote:
Rodney uses a modified version of the integrated login which performs
the=20
kinit and aklogsteps in an external process instead of relying on the
k4=20
support built into OpenAFS. More than likely he is bypassing the cause
of=20
the blue screen.
You are correct. We do use a minimally altered version of the AFS logon
authenticator "afslogon.dll" that we compile=20
ourselves. See...http://www.coe.uncc.edu/~rmdyer/afslogonshell.htm
The "altered" part is simply a single line of code addition for exec'ing
a=20
shell. But, we've only been using this method since we moved to=20
OpenAFS...since of course, I didn't have the source for Transarc's
version=20
and other reasons.
But laughing, I would be surprised if anything I do "prevents" a blue=20
screen for us! The normal "unmodified" AFS logon authenticator has
never=20
failed on me. I may be wrong, my memory is poor these days. The code
in=20
the OpenAFS authenticator DLL is pretty generic, I doubt there's
anything=20
there that would cause a blue screen as none of it runs in the kernel.
Rodney
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
------_=_NextPart_001_01C3E11E.19D4448F
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE></TITLE>
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D409392919-22012004>Okay,=20
so how does one fix it?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D409392919-22012004></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D409392919-22012004>Rich</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Jeffrey Altman=20
[mailto:jaltman@columbia.edu]<BR><B>Sent:</B> Thursday, January 22, =
2004 2:23=20
PM<BR><B>To:</B> Eggert, Richard W, II (Rich), GVSOL<BR><B>Cc:</B>=20
openafs-info@openafs.org<BR><B>Subject:</B> Re: [OpenAFS] OpenAFS + =
Linux=20
+XP<BR><BR></FONT></DIV><FONT face=3D"Bitstream Cyberbit">In this =
scenario, if=20
you are not using the MS Loopback Adapter<BR>then the OpenAFS client =
service=20
is going to crash as soon as it<BR>detects the network has =
failed. If=20
this happens while Integrated<BR>Logon is being executed and =
attempting to=20
SetToken bad bad bad<BR>things could easily be seen =
happening.<BR><BR>Jeffrey=20
Altman<BR><BR><BR>Eggert, Richard W, II (Rich), GVSOL =
wrote:<BR></FONT>
<BLOCKQUOTE=20
=
cite=3Dmid02AAAA5D0BF6DF40A6A9B07BE3124B1004CF56CF@OCCLUST02EVS1.ugd.att.=
com=20
type=3D"cite"><PRE wrap=3D""><FONT face=3D"Bitstream Cyberbit">If I =
recall correctly, I ran into the blue screens most often on my
laptop (which runs XP PRo). If I left it idle while holding AFS tokens,
the laptop would go back into standby mode, which would wipe out any
network connections. When trying to start back up, it seemed to want to
log back in, something would go wrong (probably due to the wireless
network interface not coming back up right away), and I'd get a blue
screen of death.
My memory is a bit foggy, but this is how I remember it happening.
Rich=20
-----Original Message-----
From: ted creedon [<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:tcreedon@easystreet.com">mailto:tcreedon@easystreet.com</A=
>]
Sent: Thursday, January 22, 2004 1:36 PM
To: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:openafs-info@openafs.org">openafs-info@openafs.org</A>
Subject: RE: [OpenAFS] OpenAFS + Linux +XP
Yes but he did compile it himself which often corrects whatever..
Rodney's work provides a painless way to preserve user information on a
redundant file system. It also solves the SSO problem on mixed systems.
As stated before, when BOTH AD servers crash (multiple power outages)
you're
in trouble.
tedc
-----Original Message-----
From: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:openafs-info-admin@openafs.org">openafs-info-admin@openafs=
.org</A>
[<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:openafs-info-admin@openafs.org">mailto:openafs-info-admin@=
openafs.org</A>]
On Behalf Of Rodney M Dyer
Sent: Thursday, January 22, 2004 10:20 AM
To: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:openafs-info@openafs.org">openafs-info@openafs.org</A>
Subject: Re: [OpenAFS] OpenAFS + Linux +XP
At 01:00 PM 1/22/2004, Jeffrey Altman wrote:
</FONT></PRE>
<BLOCKQUOTE type=3D"cite"><PRE wrap=3D""><FONT face=3D"Bitstream =
Cyberbit">Rodney uses a modified version of the integrated login which =
performs
</FONT></PRE></BLOCKQUOTE><PRE wrap=3D""><!----><FONT face=3D"Bitstream =
Cyberbit">the=20
</FONT></PRE>
<BLOCKQUOTE type=3D"cite"><PRE wrap=3D""><FONT face=3D"Bitstream =
Cyberbit">kinit and aklogsteps in an external process instead of relying =
on the
</FONT></PRE></BLOCKQUOTE><PRE wrap=3D""><!----><FONT face=3D"Bitstream =
Cyberbit">k4=20
</FONT></PRE>
<BLOCKQUOTE type=3D"cite"><PRE wrap=3D""><FONT face=3D"Bitstream =
Cyberbit">support built into OpenAFS. More than likely he is bypassing =
the cause
</FONT></PRE></BLOCKQUOTE><PRE wrap=3D""><!----><FONT face=3D"Bitstream =
Cyberbit">of=20
</FONT></PRE>
<BLOCKQUOTE type=3D"cite"><PRE wrap=3D""><FONT face=3D"Bitstream =
Cyberbit">the blue screen.
</FONT></PRE></BLOCKQUOTE><PRE wrap=3D""><!----><FONT face=3D"Bitstream =
Cyberbit">
You are correct. We do use a minimally altered version of the AFS logon
authenticator "afslogon.dll" that we compile=20
ourselves. See...http://www.coe.uncc.edu/~rmdyer/afslogonshell.htm
The "altered" part is simply a single line of code addition for exec'ing
a=20
shell. But, we've only been using this method since we moved to=20
OpenAFS...since of course, I didn't have the source for Transarc's
version=20
and other reasons.
But laughing, I would be surprised if anything I do "prevents" a blue=20
screen for us! The normal "unmodified" AFS logon authenticator has
never=20
failed on me. I may be wrong, my memory is poor these days. The code
in=20
the OpenAFS authenticator DLL is pretty generic, I doubt there's
anything=20
there that would cause a blue screen as none of it runs in the kernel.
Rodney
_______________________________________________
OpenAFS-info mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info">https://=
lists.openafs.org/mailman/listinfo/openafs-info</A>
_______________________________________________
OpenAFS-info mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info">https://=
lists.openafs.org/mailman/listinfo/openafs-info</A>
_______________________________________________
OpenAFS-info mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info">https://=
lists.openafs.org/mailman/listinfo/openafs-info</A>
</FONT></PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C3E11E.19D4448F--