You can't use the group name, that is true, but you can limit your homedir config file to two lines.
I have mine spread across 8 filesystems and here is my entire homedir config.
domain:*:/userdata/user2/
domain:*:/userdata/user3/
domain:*:/userdata/user4/
domain:*:/userdata/user5/
domain:*:/userdata/user6/
domain:*:/userdata/user7/
domain:*:/userdata/user1/
domain:*:/userdata/user8/
The downside of this is you really don't want to use the homedir auto create feature.
So when we privision a new users we do a mkdir /userdara/user5/avalanch00. Then when you access \\CIFSSERVER\HOME it will do a homedir database search in user2 (first in the list) but won't find /userdara/user2/avalanch00 so it will move on to user3, then user4, user5 where it will find a match. It will then keep searching the rest of the list... whatever the last match is it will make that hte users homedir. If you have auto create turned on it will look /userdara/user2/avalanch00, not find it, and make the directory. Which will, in effect, put all users on the first filesystem.
Your other option is to use regex to place the users in once place or another. Something like:
domain:[a-m].*:/path1/
domain:[n-z].*:/path2/
The advantage of that way is you turn auto-create on and it iwll make the homedir for them if it doesn't exist. Just make sure you enable regexg in your config file.
It looks like you can trim your homedir down to a few lines...
Firstly welcome to the forums and thank you for being an EMC customer.
Unfortunately there isn't any way to use the group (primary in consideration obviously of a user in more than one) that the user is a member of for directory substitution. The only variables are /Domain and /Username which you are already using. I do see value in what you are proposing, and I am also envisioning what you are doing to work-around it and can see why your homedir config file is rather lengthy (and will grow as you add more users).
Just a heads up for someone that runs across this post in the future. (Probably me in 2 years trying to figure out why it's not working for someone)
Make sure all your usernames match their homedirectory, I found 7 users that for whatever reason (legacy, typos, etc) that their home directory path was different then their username.
username: firstname
homedirectory: /home/group1/lastname
It looks like you'll have to have custom lines for those users.
cincystorage
2 Intern
•
467 Posts
892
0
Posted February 22nd, 2013 04:00
You can't use the group name, that is true, but you can limit your homedir config file to two lines.
I have mine spread across 8 filesystems and here is my entire homedir config.
domain:*:/userdata/user2/
domain:*:/userdata/user3/
domain:*:/userdata/user4/
domain:*:/userdata/user5/
domain:*:/userdata/user6/
domain:*:/userdata/user7/
domain:*:/userdata/user1/
domain:*:/userdata/user8/
The downside of this is you really don't want to use the homedir auto create feature.
So when we privision a new users we do a mkdir /userdara/user5/avalanch00. Then when you access \\CIFSSERVER\HOME it will do a homedir database search in user2 (first in the list) but won't find /userdara/user2/avalanch00 so it will move on to user3, then user4, user5 where it will find a match. It will then keep searching the rest of the list... whatever the last match is it will make that hte users homedir. If you have auto create turned on it will look /userdara/user2/avalanch00, not find it, and make the directory. Which will, in effect, put all users on the first filesystem.
Your other option is to use regex to place the users in once place or another. Something like:
domain:[a-m].*:/path1/
domain:[n-z].*:/path2/
The advantage of that way is you turn auto-create on and it iwll make the homedir for them if it doesn't exist. Just make sure you enable regexg in your config file.
It looks like you can trim your homedir down to a few lines...
Hope this helps.