has anybody had experience doing cifs.home_dir this way? i am having a problem. i'm sure i am missing something. the original post was from me and steve losen answered.
Yes, we have cifs.home_dir pointed at a directory of symlinks, and it's working fine here:
cifs.home_dir /vol/vol0/home/users/%u%/nt,/vol/vol0/home/users
This is pretty neat (for us), as the mere presence of an "nt" subdir in a user's (Unix) homedir will place their Windows homedir in that subdir. If there is no such "nt" subdir, then their top-level Unix homedir will also be their Windows homedir. Different users have different preferencs.
The only glitch I noticed was that initially, the /vol/vol0/home/ directory was a plain directory (not a qtree) on a Unix-style volume, and even though the targets of all the symlinks were NTFS-style qtree's, these auto-generated home shares ended up with Unix security style. This issue was solved by putting the symlinks in a mixed-style qtree (we use the same symlinks for both Windows and Unix users). I did put in an enhancement request about this issue (we're running 6.1R1).
Oh yeah, there is one other part necessary. The symlink.translations file has to be present and accurate, and the symlinks cannot point to targets that are _off_ of the filer. We make the symlinks on an NFS host, with paths relative to the NFS mount points, like this:
adminhost 269# mount | grep home /home on filer:/vol/vol0/home ... adminhost 270# ls -l /home/users/test lrwxrwxrwx 1 root root 32 Nov 5 1997 /home/users/test -> /disk/filer/users/myworkgroup/test adminhost 271# head -3 /disk/filer/etc/symlink.translations # Caution: CIFS should only follow symlinks to directories, # not to files. Windows apps don't know about symlinks. map /disk/filer/users/* /vol/vol0/users/* adminhost 272#
I think there's some interaction with the "cifs.home_dir_namestyle" option, as well, but can't recall exactly what it is. Ours is set to the null string (""), if that matters.
Regards,