raguiarunav wrote:

>
> I agree with what someone said above about fixing it would useful for
> Suse. I think the real issue is: why samba can't read/write/delete
> these files? And maybe a part of this issue or another one related with
> it is: why the update to Samba 3.2 caused this? (if it is the real
> cause...)
> Thanks
>
>
This is from the SAMBA LIST with the problem and solution. It might help
some of you.
<snip>
>>I use a Suse 11.0 as a Samba 3.2 PDC. The clients run XP SP3. I have
>> upgraded a few weeks ago from Suse 10.3 and now all files tranfer that I
do
>> - for example, downloading a file using a web browser - it leaves a trash
>> file named "transferd-fileone.Identifier"
or "tranferd-file:encryptable".
>>
>> The odd thing is that from Windows I can`t read/write/delete these files.
>> They appear with names like "hdje2423".
>>
>> Any help will be apreciated.

>Looks like a bug in 3.2.0 that got missed in release.
>We now handle named streams in xattrs or in a database
>but if we're not using either of those modules we should
>refuse to create them (as we did in Samba 3.0.x).

>Try this patch, should fix it - will be in 3.2.1.
>(attached to this post).

>Either that or you can add:

>vfs objects = streams_xattr

>to the share definition and the named streams will
>be correctly stored in xattr's instead (so long as
>the filesystem supports them.

I did not copy the patch, but using the above parameter might help.
--
P. V.
"We have met the enemy an he is us" Pogo