> I have my own schema for LDAP, that stores the login, name, password > and mail directory. If the home dir already exists, adding pam_ldap to > the auth entry of /etc/pam.d/system-auth allows a login, but I think > pam_mkhomedir needs more in LDAP, or one of the account/session pam > entries is missing what it needs out of LDAP.
It would be helpful to see your system-auth file... would you mind posting it? We've got a school project in process as well but we're simply doing domain authentication against the school's existing NT system. The system-auth-winbind supplied with winbind worked "out of the box" as a replacement for system-auth. After a successful login, pam_mkhomedir creates the user's home directories locally as /home/DOMAIN/userID. This works but isn't our ultimate goal. We've been working on an approach to map the domain user to their home directory on an NT server with Samba instead of creating a local home dir. My concern is that users might tend to store data in the LTSP home directory where it won't be backed up. The NT box is a clustered system that is backed up every night whereas /home data on the LTSP server will never be. I'm not trying to talk you out of creating local dirs... but I'm wondering if this might be a problem for you as well since it doesn't sound like you're planning to backup the LTSP server /home either. -Tom ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
