On 15/08/07, James Knott wrote:

...

Why not use a symlink from /home to /export/home?

Because the entry made in the LDAP server by the YaST tool, needs to have the path as /export/home, so that when a user logs into a workstation with a LDAP usrname, it should now to use /export/home on the workstation as home dir and not /home, else the user will not get his/her home dir. On the LTSP server, /export/home is an NFS export and all workstations NFS mount that to a local /export/home For people logging in from a thin client this is not a problem. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 15/08/07, James Knott wrote:

...

Perhaps I'm missing something. There's no reason for a user to need /export/home. A symlink will take care of that too.

Let's say we have Workstation A and Workstation B and the server. All home directories for all users are hosted on the server under /export/home, which is exported via NFS. All workstations NFS mount the export from the server to a local /export/home mount point. The server is also a LDAP server and all users are added to the LDAP server. Lets' say we have user john. He comes in today and sit in cubicle 1 where workstation A is. He logs in, but Worstation A does not have a local user called john, so it authenticates against the LDAP server, which tells it that the user's home directory is /export/home/john So, john can work on his files from Workstation A, via the NFS mount. Tomorrow John comes in and sit in cubicle 2 at Workstation B, he logs in, and gets his same home directory with his files (which are actually on the server). So, it does not matter which workstation or thin client a user use, they always get their files. Now, if you set up the user in LDAP and make his home directory /home/john, then when he logs into one of the workstations, it will look for his home directory in /home/john on the workstation, but it does not exist and even if it created it there, it is not his real home. Now, if we symlink /home to /export/home on the workstation, then a local user, that only use that workstation and does not make use of the server, will have a home directory on /export/home. And we don't want that. We want to keep static users and roaming users apart -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Or better yet, edit /etc/default/useradd to suit -

Did that already, but it made no difference to the YaST user manager tool. It is not using useradd to add users, but the ldap tools as it is all LDAP users, not normal UNIX users. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 16/08/07, Joe Morris (NTM) wrote:

On 08/16/2007 04:45 AM, Andre Truter wrote:

...

...

Or better yet, edit /etc/default/useradd to suit -

Did that already, but it made no difference to the YaST user manager tool.

It is not using useradd to add users, but the ldap tools as it is all LDAP users, not normal UNIX users.

It's simple. Go to Yast, Security and users, User Management, Expert Options, Default for New Users, Path Prefix for Home Directory, and change from /home/ to /export/home/

That option is only for local users and it is the same as editing /etc/defaults/useradd, but your suggestion did improve my vision a bit as next to the Exper Options button, is the LDAP Options button with "LDAP User and Group Configuration", where you can edit the LDAP templates. I found the correct template and changed it and now it works! Thanks -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org