Hi All,

 

I'm just migrating from a Netgear ReadyNAS Duo to an unRAID box built with a HP N36L Microserver. As I've got a number of Mac clients, AFP support it important, which is why I'm running the 5.0beta.

 

When copying files to the unRAID AFP share, I'm finding that files with resource forks are causing the creation of many ._ files.

 

e.g. If I copy a file in my /media share, and it has a resource fork, I see:

 

stardust.png

._stardust.png

 

in the directory listing (I'm showing hidden files on the Mac).

 

Interestingly, this same file when copied to the ReadyNAS over AFP does not result in the creation of the ._ file. However, the resource fork data (which is what's in the ._ file) is intact on the ReadyNAS. Given that the ReadyNAS is also running netatalk, does anyone know how to prevent the unRAID version from creating these files?

 

I've tried comparing configuration files etc., but can't seem to see anything which might be related to the issue.

 

Also, I've noticed that when I change any configuration files under /etc, my changes are gone when I restart the array. I'm guessing there is a way to make these changes persistent, but I've not found it. Can anyone point me in the right direction?

 

Thanks,

 

Andy.

 

the ._ files I am not sure about, though there is an unMenu package to delete them.

 

As for the changes not being saved, that is because unRAID runs from RAM. If you want to change anything you will need to replicate the steps and put then in the go script that is in the config folder.