Before the system hangs, it mounts the NFS shares as well as the snapshot directories, also on NFS... Stephen Goggin Test Engineer NetEffect, Inc. 9211 Waterford Centre Blvd. Austin, TX 78758 Email: sgoggin@xxxxxxxxxxxxx 512.493.3232 :Desk 512.983.1939 :Mobile 512.493.3393 :Fax -----Original Message----- From: The Big Guy [mailto:HotShit@xxxxxxxxxxxx] Sent: Thursday, November 01, 2007 8:17 AM To: Stephen Goggin Cc: pam-list@xxxxxxxxxx Subject: RE: How do I...? The suggestion I was making was regarding the real /etc/pam.d on the PXE server. I.e. boot up a regular RedHat (or Ubuntu if you just want a LiveCD test) on one of the PXE client/workstation machines, then try mounting the NFS share off the PXE server. My assumption from your description(s) is that this will fail with the credentials that you are using. ----- Original Message ----- >From: "Stephen Goggin" <sgoggin@xxxxxxxxxxxxx> >To: "The Big Guy" <HotShit@xxxxxxxxxxxx> >Subject: RE: How do I...? >Date: Thu, 01 Nov 2007 00:18:11 -0500 > > I followed this how-to on getting PXE running: > http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-gui > de/ch-pxe.html > > On the PXE server, I have 2 directories relating to the client image: > /diskless/root/ and > /diskless/snapshot/192.168.55.xxx/ > > The root directory is your primary boot information. The snapshot > directory is for variable read/write information. All clients have r/w > access to their own respective snapshot directories... > > In the /diskless/root/etc/pam.d/ directory is where I'm making changes, > which propagates to all the clients... > > The pam.d directory is in the root, not snapshot. It's the same for all > clients... > > I'm not making it up that this has happened before... I modified a file > in the /diskless/root/etc/pam.d/ folder, commented out a line, and it > all worked fine afterward. That is, until we made a new PXE image, and > the previous modifications were overwritten... > > So, I need 1 of 3 things: > 1. What file do I modify, and what line do I comment out? > Or > 2. How do I disable PAM completely? > Or > 3. How do I build RHEL4U4, FC4, or FC5 image with no PAM on it? > > > Does anyone have the information on any of those 3 things? > > > > > > > Stephen Goggin > > Test Engineer > NetEffect, Inc. > 9211 Waterford Centre Blvd. > Austin, TX 78758 > Email: sgoggin@xxxxxxxxxxxxx > > 512.493.3232 :Desk > 512.983.1939 :Mobile > 512.493.3393 :Fax > > -----Original Message----- > From: The Big Guy [mailto:HotShit@xxxxxxxxxxxx] > Sent: Wednesday, October 31, 2007 5:51 PM > To: Stephen Goggin > Cc: pam-list@xxxxxxxxxx > Subject: RE: How do I...? > > > Hello, > > > > Oh? Where? I've Googled for it for days now and have > > never found one... > > Is it compatible with a PXE booting NFS situation? > > He meant the post you got a couple of days ago regarding > the permit module. > > The interesting thing now is that you mention NFS on > your PXE boot. Have you tried changing the PAM on > the Server, rather than the PXE Client, image? This > would be the thing that would stop the local init .. the > kernel/init bails when it can't find a file system .. if > you can't auth to your NFS share then you'd be set for > failure. > > > FWIW your requirements still sound screwy. In the > 6Mbyte distro that I built (that boots out its own PXE > children); I let it build a fully meshed SSH network > by dynamically sharing the public SSH keys (as > generated on each boot) via my own daemon. This > would give you exactly what you want (without > breaking PAM). > > But then, I don't think this is your problem; check your > NFS setup - particularly at the head-end. > > > > > > > -- > RingBurn.com > "Where there's smoke, there's fire" > > _______________________________________________ > Pam-list mailing list > Pam-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/pam-list > -- RingBurn.com "Where there's smoke, there's fire" _______________________________________________ Pam-list mailing list Pam-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/pam-list
