Did a quick search. Found.
http://www.thecus.com/products_over.php?cid=10&pid=77
http://diet-pc.wiki.sourceforge.net/thecus_n4100plus

While it may be possible to hack the NAS, I probably would not. The XP script does the job, leave it as is. Much less risk and little to gain unless you really want to hack the beast.

del m:\.recycle\*.tmp /S /Q
del m:\.recycle\*.db-journal /S /Q
del m:\.recycle\*.db-stmtjrnl /A:H /S /Q
del m:\.recycle\*.MMSaTe /S /Q

It's a Thecus N4100pro, a Soho type. I only have the option "Samba recycle bin enable/disable".
For the present, scheduled tasks on the XP Clients are deleting (only) the journal files.
But I will refresh my dusty Linux knowledge, so I can install a cronjob on the NAS.

Edit 2008-12-09, 8:40 GMT:
OK Owyn, I'll let it be. There exists a shell module for the NAS, but Linux isn't my daily profession so I'll make no experiments.

For those, who have a similar Problem: there are some hidden files
[code]
del m:\.recycle\*.tmp /S /Q
del m:\.recycle\*.db-journal /S /Q
del m:\.recycle\*.db-stmtjrnl /A:H /S /Q
del m:\.recycle\*.MMSaTe /S /Q
[/code]

what kind of nas is it? I have a readynas NV+ and I am pretty sure that there is an option for the recycle bin to automatically clear itself after a some time period (days?).

Ok. If it's based on the db engine, I have to continue with my del. script.
Thanks for the infos, Timo

Yep.
The problem would never show up for 99.99%+ of users.

SQLite (the embedded database in MM3) is not designed for network use. This is just one of the artifacts of that fact.

MM3 would have to make a major change to use something like embedded MySQL (as Amarok2 did) to properly support a networked install.

For now, I think you will have to continue to live with the, I assume, cron scripts.

Some NAS auto add delete files to the Recycle Bin so that the user can recover them. I assume that locally the file is removed permanently.

The issue here seems that the NAS has a non-standard implementation of the Recycle Bin.

I do not have any either.

Nyn

It's not really part of MM code, it's the database it uses which generates it/them.
It also must be NAS specific as these do not end up in my recycle bin

Your are generating a MM-db-journal, that is deleted after use.
My DB resides on a NAS with recycle bin.
I delete all the entries with a time triggered script, but...
Isnt't it better to reuse this file instead of generating and deleting it all the time?