Bug 55542 - dot files not hidden
Summary: dot files not hidden
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: samba (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-11-01 19:38 UTC by Michal Jaegermann
Modified: 2007-04-18 16:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-11-03 19:04:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Michal Jaegermann 2001-11-01 19:38:06 UTC
Description of Problem:
With samba-2.0.10-2 (the last one from updates to RH 7.1) I have
"hide dot files=Yes", which is confirmed by 'testparm', but on a client
all these dot files do show up - at least in a "[Homes]" share.
Cosmetic but the real user of this client is tad confused.

Comment 1 giulioo 2001-11-03 18:46:13 UTC
With "hide dot files" dot files are served as "hidden", this means the win 
client may or may not show them to the user, depending on how it's confgured 
(explorer, view, folder option, ..).

I think you want "veto files": files in this list will not be served at all.

veto files = /.*/

Comment 2 Michal Jaegermann 2001-11-03 19:03:12 UTC
Re-reading 'man smb.conf' I do not think that I would really want "veto files".
A number of possible side-effects, including but not limited to performance
impact, is too great.  "Hide dot files" _should_ be it.
OTOH maybe the problem is really on a client side and its file browser
configuration?  Looking at the manual closer Samba does not really "hides"
these files but is only setting an attribute "hidden".  As this is not on my
client and/or network I will likely be able to check that only in few days.
My meagre knowledge of Windows is possibly showing. :-)

Comment 3 Trond Eivind Glomsrxd 2001-11-06 19:34:23 UTC
As long as the proper attribute is set, this is a windows filebrowser
configuration issue. Closing.

Note You need to log in before you can comment on or make changes to this bug.