Quote:
Originally Posted by weigenmann Down at Edit /etc/pam.d/common-session where you are asked to insert
session required pam_mkhomedir.so skel=/etc/skel umask=0077
When I insert the above line into /etc/pam.d/samba instead it does actually create the users home directory without the work around. |
I've attempted to add the line as well. It didn't work for me. It appears we are using the same OS (Cent OS 5 x86_64) so I'm not sure what the difference is.
We've reviewed my last posting though and found error in it. Here's where I am now...
Code:
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth required pam_env.so
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 500 quiet
auth sufficient pam_ldap.so use_first_pass
auth required pam_deny.so
account required pam_unix.so broken_shadow
account sufficient pam_succeed_if.so uid < 500 quiet
account [default=bad success=ok user_unknown=ignore] pam_ldap.so
account required pam_permit.so
password requisite pam_cracklib.so try_first_pass retry=3
password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok
password sufficient pam_ldap.so use_authtok
password required pam_deny.so
session optional pam_keyinit.so revoke
session required pam_limits.so
session optional pam_mkhomedir.so
session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
session required pam_unix.so
session optional pam_ldap.so
Most of the essential rows and columns have been isolated and tested in this file. The one that seems to hold everything up has been tagged.
This file
is auto-generated as the comment implies. After
each testing of authconfig you should:
a) change all 'sufficient' to 'required' and
b) comment out OR delete the line in question.
c) test it
Personally, I've backed up mine and restore if I need to run authconfig again. All I will say is that it works for me

===
Now, for the benefits. As this file is now more flexible than in my original posting, it still satisfies the same requirements:
1) my test users can login via the samba domain
2) their home directories are created automatically
3) the server can still find it's self when starting (after a reboot) and boot normally
4) you can still login as root
...but now does not require any further changes to any other PAMs.
I am
still not an expert with PAM.