Quote:
Originally Posted by bmynars
I have exactly the same issue running on OpenSuSE 11.0, samba 3.2.0-22.1, so it is not isolated to the originator of this post. Suggesting creating a 'cron' job does not seem to be the right solution but only a 'work around'.
It appears that OpenSuSE 11 has many more quirks than one would wish for. Can anyone on the SuSE team seriously look into this? Eventually, this will be rolled up into Novell Enterprise product and when it does, please, believe me, I will come after Novell with a heavy hammer to have it fixed. We are running many SuSE Enterprise servers and having unwanted files created during each file transfer is something I am really not looking forward to.....
|
To anybody who is interested in making sure that *.Zone.Identifier:* files are not created during the transfer, please, add following to your GLOBAL section in samba config file:
veto files = /*.Zone.Identifier:*/
This will prevent those files from being created. Warning: any files that would be named in a similar fashion will not be allowed on the Samba server when you set it up that way. However, I'd rather have this than a 'cron', yet another unnecessary job running for something that the system is not supposed be doing anyway.