samba - Oct 2016 - smb.conf veto files entry question

While working on my existing member file server smb.conf config file I
found an entry for "veto files" like the following: 

veto files = /.bash_logout/.bash_profile/.bash_history/.bashrc/ 

The "man smb.conf" entry says: 

veto files (S)

           This is a list of files and directories that are neither
visible
           nor accessible. Each entry in the list must be separated by a
'/',
           which allows spaces to be included in the entry. '*' and
'?'
can be
           used to specify multiple files or directories as in DOS
wildcards.

           Each entry must be a unix path, not a DOS path and must not
include
           the unix directory separator '/'.

           ..... snipped for brevity ..... 

Am I reading a contradiction? 

First paragraph says "Each entry in the list must be separated by a
'/',
which allows spaces to be included in the entry." 

And then the next paragraph says: ". . . . must not include the unix
directory separator '/'." 

What? Can anyone explain? 

-- 
_______________________________

Bob Wooden of Donelson Trophy

There's no contradiction. '/' is used to separate filenames in veto
files, therefore it
cannot be a part of the underlying file name. This means you cannot have
/path/to/vetofile
specified, just vetofile. I've never used veto files, but I assume once you
specify it,
these files will be hidden on matter where they are in the share subtree.



Em 27/10/2016 10:25, Bob of Donelson Trophy via samba
escreveu:
> While working on my existing member file server smb.conf config file I
> found an entry for "veto files" like the following:
>
> veto files = /.bash_logout/.bash_profile/.bash_history/.bashrc/
>
> The "man smb.conf" entry says:
>
> veto files (S)
>
>             This is a list of files and directories that are neither
> visible
>             nor accessible. Each entry in the list must be separated by a
> '/',
>             which allows spaces to be included in the entry. '*'
and '?'
> can be
>             used to specify multiple files or directories as in DOS
> wildcards.
>
>             Each entry must be a unix path, not a DOS path and must not
> include
>             the unix directory separator '/'.
>
>             ..... snipped for brevity .....
>
> Am I reading a contradiction?
>
> First paragraph says "Each entry in the list must be separated by a
'/',
> which allows spaces to be included in the entry."
>
> And then the next paragraph says: ". . . . must not include the unix
> directory separator '/'."
>
> What? Can anyone explain?
>
-- 

	
Vinicius Silva
SOC


BRA: + 55 51 2117.1000 | 55 11 5521.2021
USA: + 1 888 259.5801
vbs at e-trust.com.br
skype: vinicius.bones.silva

	







	Smiley face

www.e-trust.com.br <http://www.e-trust.com.br/>


Esta mensagem pode conter informações confidenciais ou privilegiadas. Se você
recebeu esta
mensagem por engano, você não deve usar, copiar, divulgar ou tomar qualquer
atitude com
base nestas informações. Solicitamos que você apague a mensagem imediatamente e
avise a
E-TRUST, enviando um e-mail para suporte at e-trust.com.br. Opiniões, conclusões
ou
informações contidas nesta mensagem não necessariamente refletem a posição
oficial da
E-TRUST. Caso assinada digitalmente, a autenticidade desta mensagem pode ser
confirmada
pela Autoridade Certificadora Privada E-TRUST, disponível em www.e-trust.com.br.

This message may contain privileged and confidential information for the use of
the
intended recipients only. If you are not an intended recipient then you should
not
disseminate, copy, or take any action based on its contents. If you have
received this
message in error then please notify E-TRUST by sending an e-mail message to 
suporte at e-trust.com.br immediately. Views and opinions expressed in this
message do not
necessarily reflect the position of E-TRUST. If this message is digitally
signed, its
authenticity can be confirmed by E-TRUST Private Certificate Authority,
available at
www.e-trust.com.br.