From: jam <ja...@ti...> - 2009-04-30 00:47:58
|
On Wednesday 29 April 2009 15:53:20 lts...@li... 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. How about (and this is very easy to automate) every year or every term whatever Remove all learn-users Add a list that you create every period eg list jonny.c susy.q etc what ever scheme you choose Tag the comment field with #a tag that helps you manage them We do that for our customers. perl was a friend. Admin overhead is creation of a unique list periodically (my plebs can use nano easily) and a Create-script and you want a Reset-script. Object achieved without drama. Read and heed Scott's message Every user logs in as their name and with the password you choose in your scheme eg passwd per class per school whatever James |