Jordan Erickson wrote: > I would propose a "temporary" user of sorts that pulls from the > "skel/template" you created, does a pam makehomedir or whatever it is, > and removes it upon logout. This way, you have separate user accounts > for each login, and changes can be wiped upon user logout.
The immediate problem with this is how to keep control over the different usernames/passwords currently in use. Now it's easy just telling all students to use "student/student" to log in. If we have to inform them to use random usernames/passwords, then it'll quickly become a user administration nightmare. But maybe you meant some other way of creating the accounts..? It needs to be simple and predictable. - Marius ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _____________________________________________________________________ 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.freenode.net
