samba - Jan 1999 - Like Netware share ??

Most of you will probably think about this "It's not a real
problem". But not my boss. I want to
exchange our Netware server with a linux/SMABA one but my boss wants to have on
the new server
exactly the same directories structure like in the Netware server. And here it
is what I couldn't
done : user X  wich have two secondary groups Y and Z must browse in Win95
_only_  the Y and Z
shares (and homedirectories share, of course). This is done already with home
share !
Please help Samba to win a new user.

>Most of you will probably think about this "It's not a real
problem". But
not my boss. I want to
>exchange our Netware server with a linux/SMABA one but my boss wants to
have on the new server
>exactly the same directories structure like in the Netware server. And
here it is what I couldn't
>done : user X  wich have two secondary groups Y and Z must browse in Win95
_only_  the Y and Z
>shares (and homedirectories share, of course). This is done already with
home share !
>Please help Samba to win a new user.
I think what you are saying is that you want user X to only see shares Y
and Z when they open the machine, correct?

What you want to do is use samba's macro expansion with include files.  My
setup requires this also.  For example, I have a series of config files
that define shares:

smb.conf.share1
smb.conf.share2
smb.conf.share3

Then I have configuration files for each user

smb.conf.usera contains:
    include = smb.conf.share1
    include = smb.conf.share2

smb.conf.userb contains:
    include = smb.conf.share2
    include = smb.conf.share3

And in the main smb.conf file, I have

    include = smb.conf.%u

Note that the %u gets expanded to the username, so usera only gets shares
share1 and share2 defined, and userb only gets share2 and share3 defined.
And that is all they can see, and access.  As far as userb is concerned,
share1 doesn't exist.

You might have to include the full path of the conf file -- I did in mine.
Also, I found it easier to define one share per file and then combine those
into the user conf files, this way, rather can copy and pasting the share
definitions into each file, I'm sure everyone is accessing the share with
the config and permissions, and I only need to remember to change one file
when the share config changes.

My setup is actually slightly more complex, and I have used symlinks to
point to group named conf files.

Andy.

> > > I think what you are saying is that you want user X to only see
shares Y
> > > and Z when they open the machine, correct?
> > >
> > > What you want to do is use samba's macro expansion with
include files.  My
> > > setup requires this also.  For example, I have a series of config
files
> > > that define shares:
> >
> >   Weird that this works, I read some time ago on this Samba mailing
list
> > that during browsing through Samba shares, no user credentials are
being sent
> > to server and the first authentication is being made during the
connect to
> > the specific share itself. Are you sure that this works? Maybe that
other guy
> > was wrong if you're OK.
> 
> As far as I know, it works great with Win95.  All but one of the machines
on my
> network are WinNT4 (the other one is a win95).  There is a problem with
WinNT
> when browsing shares -- it wants to refresh the share list ANONYMOUSLY a
second
> time after opening a share. The way username assignments are setup, this
causes
> all sorts of havoc with macro expansion, and shares suddenly
'disappear'.  I have
> written a patch for samba to 'restrict anonymous' connections,
which greatly
> increases the reliablity of this (there are still a few problems, and
shares are
> known to disappear, but these times are rare as far as I know, and ms's
netbios
> stack seems to not want to put things in the same order in the packets in
95 as
> it does with NT, but this is beyond the scope of what I can even attempt to
> fix).  It is at www.reac.com/samba/ look for files named samba-restanon*. 
But
> you shouldn't need this patch if you use only win95.
> 
> I'd say give the macro stuff a try and see how it goes.
  Thanks for explanation, I'll giving CC to samba@samba.org as you
hadn't done
it yourself and I found your answer as a good information to spread it to the
world. :-)
> Andy.
> Andy Bakun <abakun@reac.com>