homes share and logon path

[Mike Rylander]

Here is how I solved this problem:

[globals]
   .
   .
        logon path = \\%N\profiles
        logon drive = h:
        logon home = \\home_dir_server\%U
   .
   .

[profiles]
        path = /home/%U/profile
        read only = No
        guest ok = No
        browseable = no

Then create the profile directory in each home dir (/home/*).  %U is 
reinterpreted each time windows connects to samba, and samba is doing the 
translation, so windows isn't involved.  To simplify admin, I am NFS mounting 
/home from home_dir_server so that the users profile is in his global unix 
home directory.  And as far as I know, the [homes] shares are the only shares 
that hangs around.  NOTE:  your windows and unix usernames must be exactly 
the same, including case, for this to work.

-- 
Mike Rylander
Senior Unix Administrator
Incanta, Inc.

On Saturday 05 May 2001 23:59, you mumbled homes share and logon path:
> The Smamba 2.2 PDC FAQ says it is bad to set "logon path =
> \\%N\%U\profile" in smb.conf, because sometimes Windows clients will
> maintain a connection the \\homes\ share after the user has logged out.
>
> I'm just trying to understand this.  When /does/ Windows drop a
> share?  Setting up a [profiles] share as /home/%U/ would suffer the same
> problem I take it?  And the trick, then, is appending %U to a shared
> share (so to speak), not making %U part of the share itself.  Correct?
>
> I would really like to keep /home/<username> a one stop shop for a
> person's stuff, including roaming profile data.  Is there a good way
> to do this?  A [myhomes] share pointing to /home, and "logon path =
> \\%N\myhomes\%U" perhaps?  Yes/No/Maybe So?