[EMAIL PROTECTED] wrote: > > Hello, > > I think my typo may have been the problem after all. Doh! > > It seems to be working properly now. > > A couple of additional things I've noticed: > > 'obey pam restrictions' must be set to yes to get the pam_mkhomedir module to do its >job.
Yes - otherwise we don't execute that code. If people don't have PAM setup, it would fail :-( > The homes share must have /home/%D as the path. /home/%D/%U, and blank does not >work. This connects the user to a share named after the login ID, but >double-clicking that share shows all of the folders in the /home/%D path rather than >just the contents of the user's folder. Which makes sense, but why doesn't >/home/%D/%U or a blank entry work? > > Thanks to everyone for your assistance. A blank entry should work - in what way does it 'not work'? Try 2.2.6rc2 - a stat() check has been removed that might have caused the problem. Samba 3.0 has even more advanced logic here. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
