samba - Apr 2017 - Setting up a Share Using Windows ACLs

On 2017-04-25 19:05, Rowland Penny wrote:
> On Tue, 25 Apr 2017 18:52:30 +1000
> Henry via samba <samba at lists.samba.org> wrote:
> 
>> 
>> Thanks Rowland, you are correct.
>> My share folder name with a space was escaped using "\" and I
do have
>> another test share with a space in the folder name that works !
>> So changing the folder name to something new makes it work and if
>> changed back it stops working so somewhere there must be a memory of
>> the old folder name with retained config problems.
>> I bet it's stored in a Samba db or similar however this is beyond
my
>> skill set.
>> 
> 
> Did you restart the Samba deamons after making the changes ?
> 
> Rowland
Yes, fully rebooted member server just to be sure.

On Tue, 25 Apr 2017 19:13:53 +1000
Henry via samba <samba at lists.samba.org> wrote:
 
> > Did you restart the Samba deamons after making the changes ?
> > 
> > Rowland
> 
> Yes, fully rebooted member server just to be sure.
> 
That should have cleared on local Samba caches, so I wonder if there is
a windows cache involved here.

What I do think is, it isn't a good idea to create Samba shares with
spaces in the name, use an underscore instead.

Rowland

On 2017-04-25 19:32, Rowland Penny wrote:
> On Tue, 25 Apr 2017 19:13:53 +1000
> Henry via samba <samba at lists.samba.org> wrote:
> 
>> > Did you restart the Samba deamons after making the changes ?
>> >
>> > Rowland
>> 
>> Yes, fully rebooted member server just to be sure.
>> 
> 
> That should have cleared on local Samba caches, so I wonder if there is
> a windows cache involved here.
Where would I look for a Windows cache as Samba is both Domain 
Controller & Member Server?
I'll try running RSAT on a different Windows client and see if there is 
any difference.
> 
> What I do think is, it isn't a good idea to create Samba shares with
> spaces in the name, use an underscore instead.
> 
> Rowland

> What I do think is, it isn't a good idea to create Samba shares with
> spaces in the name, use an underscore instead.
Why? I have been using shares with spaces in their names for years 
without running into problems even once.

Windows fully supports it, so should and does Samba.

In a business environment you NEED proper, human readable names, not 
ugly convoluted substitutes.

Just declare the names in smb.conf as they are, without trying to escape 
anything. It just works.