As a general comment your smb.conf file seems overly complex for a home
user. I dunno where all those options came from - perhaps you disto did
them? I don't necessarily advocate changing them, but they do all
require understanding. My shares are generally pretty simple.
On Fri, 09 Sep 2005 08:21:12 +1200
Roger Searle wrote:
> [users]
> comment = All users
> path = /home
> read only = No
> inherit acls = Yes
> veto files = /aquota.user/groups/shares/
The effect of this veto files line is to make sure the clients do not
see any file called "aquota.user" or "groups" or "shares"
The quota bit sticks out as perhaps something to do with disk space
appearing to run out.
Here is an extract from man smb.conf:
<quote>
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 '/'.
Note that the case sensitive option is applicable in vetoing files.
One feature of the veto files parameter that it is important to be aware of
is Samba's behaviour when trying to delete a directory. If a directory that is
to be deleted contains nothing but veto files this deletion will fail unless
you also set the delete veto files parameter to yes.
Setting this parameter will affect the performance of Samba, as it will be
forced to check all files and directories for a match as they are scanned.
Default: veto files = # No files or directories are vetoed.
Example: veto files = ; Veto any files containing the word Security, ; any
ending in .tmp, and any directory containing the ; word root. veto files =
/*Security*/*.tmp/*root*/ ; Veto the Apple specific files that a NetAtalk
server ; creates. veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash
Folder/
</quote>
--
Nick Rout <[EMAIL PROTECTED]>
