How can I *veto* dot files? The naive approach of using /.*/ fails in so far as no file at all appears on the NT side :-) Hiding isn't enough for me, as I do want to see all hidden files on the NT side of things - I just don't want to see the Linux dot files on the NT side. This is Samba 2.0.6 (RH6.2) with the below configuration. TIA, Stefan ************ # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Date: 2000/07/04 20:23:40 # Global parameters [global] netbios name = STEFAN-Z600 server string = Samba Server encrypt passwords = Yes log file = /var/log/samba/log.%m max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 local master = No dns proxy = No [homes] comment = Home Directories read only = No veto files = /.*/*.tmp/ browseable = No [printers] comment = All Printers path = /var/spool/samba print ok = Yes browseable = No [test] comment = Linux data path = /export/data read only = No guest ok = Yes
On Wed, 5 Jul 2000 04:35:48 +1000, you wrote:>How can I *veto* dot files? >The naive approach of using > /.*/ >This is Samba 2.0.6 (RH6.2) with the below configuration.This is a bug that is solved in 2.0.7. -- giulioo@pobox.com
At 04:35 05/07/00 +1000, you wrote:>The naive approach of using > > /.*/ > >fails in so far as no file at all appears on the NT side :-) Hiding isn'tPossibly this is a bug in 2.0.6, or I'm missing something else about your configuration. I just defined the following share in Samba 2.0.7 on RH6.2 (with 2.2.16 kernel): [myhome] comment = Personal home directory for %U path = %H public = no writable = yes create mask = 640 directory mask = 750 veto files = /.*/*.tmp/ And the veto files option appeared to do exactly what you want, all the dot files and all files ending in .tmp appeared to be absent, everything else was normal. Try setting up the same share on your box and see what happens, if it doesn't work then I suggest getting the Samba 2.0.7 RPM from one of the mirror sites. n.b. I was accessing this from Win95, does anyone know if it's possible that the effect of veto files could be in any way client dependant? -- Who is this General Failure, and why is he reading my hard disk?
Apparently Analagous Threads
- Veto files option not working
- Can't see all of the directories in a share with 2.2.7a-1 &RH8...but older version/kernel can
- 2.2.4 and "veto files" -> cpu maxed out
- Can't see all of the directories in a share with 2.2.7a-1 & RH8...but older version/kernel can
- large file support