samba - Apr 2002 - Home share stay in list

Hi,

I've already saw that many other users have the same problem, so I am
interested if somebody have adequate solution for this.

In short: Samba 2.2.3a, clients Windows 2000 Pro, with many users on the
same machines. When new user log in, he or she can see all previous used
home shares, even he/she cannot see inside other's shares. But, it is so
irritant having dozen of user's shares in browse list.

Restarting Samba clears that old unused shares, but this is not a solution.
Because of that, I think that the problem is in nmbd cache, which cache is
not aranged when some user logoff.

Thanks for any idea.

--
Ivan Gustin

On Sat, Apr 27, 2002 at 11:15:37PM +0200, Ivan Gu?tin
wrote:
> Hi,
> 
> I've already saw that many other users have the same problem, so I am
> interested if somebody have adequate solution for this.
> 
> In short: Samba 2.2.3a, clients Windows 2000 Pro, with many users on the
> same machines. When new user log in, he or she can see all previous used
> home shares, even he/she cannot see inside other's shares. But, it is
so
> irritant having dozen of user's shares in browse list.
> 
> Restarting Samba clears that old unused shares, but this is not a solution.
> Because of that, I think that the problem is in nmbd cache, which cache is
> not aranged when some user logoff.
Incorrect.  This is correct behaviour.  The [homes] share dynamicly creates
the extra shares as they (or [homes] itself) are accessed.  The client
is keeping the connection open, causing this behaviour.

We can't have different share lists for different users very easily, becouse
a 'tree id' for the connection to the tree is valid for all vuids (user
connections)

Andrew Bartlett

Hi again,

I found a workaround for the problem I mentioned before.

I renamed [homes] section to [personal], and set 'browseable = yes'.
This
change wouldn't create new share for each logged user and produce so many
shares from user's name, but will create the same share name each time with
different user's home path.

With this, share has always the same name, but points to each user's home
directory, without producing so many shares. The only disadvantage is that
user's home directory is not displayed as user's login name, but always
is
named 'personal'. IMHO, that will be less confusing to dumb users (lost
in
finding his or her short login username).

So, instead previous:
--------------------
[homes]
        comment = Personal directory of user %U
        read only = no
        create mask = 0600
        directory mask = 0700
        browseable = no
        writeable = yes
--------------------

I use now:
--------------------
[personal]
        path = /home/%U
        comment = Personal directory of user %U
        read only = no
        create mask = 0600
        directory mask = 0700
        browseable = yes
        writeable = yes
--------------------

And that's work fine for me. What do you think on this workaround?

--
Ivan Gu?tin, ivan@elin.hr, (098) 366-346
ELIN Elektronika i informatika, www.elin.hr, (052) 623-491
Lindarska cesta 1, 52000 Pazin



----- Original Message -----
From: "Ivan Gu?tin" <ivan@elin.hr>
To: <samba@lists.samba.org>
Sent: Saturday, April 27, 2002 11:15 PM
Subject: [Samba] Home share stay in list

> Hi,
>
> I've already saw that many other users have the same problem, so I am
> interested if somebody have adequate solution for this.
>
> In short: Samba 2.2.3a, clients Windows 2000 Pro, with many users on the
> same machines. When new user log in, he or she can see all previous used
> home shares, even he/she cannot see inside other's shares. But, it is
so
> irritant having dozen of user's shares in browse list.
>
> Restarting Samba clears that old unused shares, but this is not a
solution.
> Because of that, I think that the problem is in nmbd cache, which cache is
> not aranged when some user logoff.
>
> Thanks for any idea.
>
> --
> Ivan Gustin
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>