> Do the home directories get created when the user first logs in, then? thats right. pam_mkhomedir.so
> * If you are tolerant of seeing "errors" in your Puppet logs, you > could go ahead and define the keys; Puppet won't put them in place if > the directories aren't there. I don't advocate this approach, but it > is one I've seen used. this has been the state of things for a while. error spam has gotten a little out of hand. > * If the users are *allowed* to log in to the servers in question, and > the directory would be created on first login, go ahead an > pre-populate it with Puppet instead. It doesn't cause any harm and > saves you some headaches since you won't be fighting your tools. > Seriously, what are you trying to save here? i'll think about this approach. > * This is only a vaguely formed idea, but you could populate a set of > <username>_homedir_exists custom facts that basically check if the > home directory exists. Then you could declare all of these > ssh_authorized_key resources dependent on those facts... I haven't > totally thought that through, but it could work. don't know how i would make a File depend on a fact. think i'd end up approaching a problem similar to the one i'm trying to solve. > --Paul > Another option, which may be valid, is that SSH supports moving the > user's SSH authorized_keys files out of the user's home directories. > If you're already managing the SSH daemon with puppet this is pretty > simple to do. this is a really good idea ! > - A. benjamin - wishing File supported refresh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
