Very nice solution.
Thanks a lot.
BR Rene
On Jun 10, 6:08 pm, paul matthews
wrote:
> An alternate, non Puppet method is to add a pam_mkhomedir module to
> /etc/pam.d/system-auth (on a RedHat machine at least) by including the
> following line:-
>
> session required /lib/security/$IS
On Wed, Jun 10, 2009 at 12:08 PM, paul matthews <
paulsmatth...@googlemail.com> wrote:
> An alternate, non Puppet method is to add a pam_mkhomedir module to
> /etc/pam.d/system-auth (on a RedHat machine at least) by including the
> following line:-
>
> session required /lib/security/$IS
An alternate, non Puppet method is to add a pam_mkhomedir module to
/etc/pam.d/system-auth (on a RedHat machine at least) by including the
following line:-
session required /lib/security/$ISA/pam_mkhomedir.so skel=/etc/skel
umask=0022
This has the effect of creating a homedir if one do
Rene wrote:
> In our environment, we have a non standard /etc/skel directory. The
> content of that directory is managed via puppet. How do I guarantee,
> that the content of that directory is on the system before a user is
> created. Do I need a require attribute on every user creation
> statement