|
|
You are right - but aMule is actually creating new files. bak files are backup copies. When creating such a backup copy, the creation of new files is involved for security reasons. (i.e. first create a new file with the backup, then delete the old backup file and rename the new backup file)
aMule uses standard permissions for files, i.e. the permissions a file would get when you created it manually. This is done using the so called umask.
(Calculation: 777-umask value, all octal; example: umask=022 -> 777-022=755 means owner can do everything and group and other can't write, but read and execute. Please read more about Unix file permissions for details.)
NTFS doesn't support Unix File permissions. Therefore, setting the umask to 0 is a possible solution. But this is more a problem where your distribution's help forum can assists you than a problem where aMule developers can help you. |
|