Description of problem:
Recently replaced pam_mkhomedir with oddjob-mkhomedir to work around the SELinux issues with pam_mkhomedir. There appear to be some general man pages for oddjobd and oddjobd.conf, but no documentation anywhere that I can find for how to configure oddjobd-mkhomedir.conf.
More specifically I was trying to figure out how to specify the skeleton directory in oddjobd-mkhomedir.conf, since you can't pass arguments via /etc/pam.d/password-auth like you could with pam_mkhomedir.
The man pages for pam_oddjob_mkhomedir explicitly tell you that you can't pass arguments directly to the module, but doesn't tell you how to pass them via oddjobd-mkhomedir.conf. Since I knew how this parameter was passed using the original pam_mkhomedir, I was able to guess correctly what the parameter should look like. But in my opinion this needs to be documented somewhere.
Another possible bug is that oddjobd-mkhomedir does not use /etc/skel as the default skeleton directory (pam_mkhomedir does). Not sure if this is the intended behavior, but this is the reason why I had to figure out how to pass the skel parameter to oddjobd-mkhomedir. It would be nice if this were more consistent.
Version-Release number of selected component (if applicable):
It's a missing man page, should be 100%
Steps to Reproduce:
If oddjob_mkhomedir is already installed:
1. man pam_oddjob_mkhomedir [works]
2. man oddjobd-mkhomedir.conf [does not work]
No manual entry for oddjobd-mkhomedir.conf
Even if there's no man page for this conf file specifically, there needs to be some documentation somewhere on how to pass arguments via oddjobd-mkhomedir.conf
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.