Jump to content

write permissons for seeding only. why?


hunterr9

Recommended Posts

hi!

firstly _Thanks_ for utorrent for Linux!

Works Fine,

but...

why not to check permissions for writing NOT BEFORE, but AFTER hash checking,

and if all sums are matched, don't check for writing permission at all?

what does utorrent need to write to completed or new files?

nothing to download!

more deeply:

if we have completed files, or files with newly created torrents,

server trying to check it permissions for write-access before

calculating and comparing check-sums...

and if it is r/o access - gives up with an error.

any start for seeding is starting from such check.

made some tests: if we can remount that volume with r/w perm.,

and recalculate hash, it works, but if permission will be changed

to r/o back, next start to seed will fail...

--

reasons:

if we have, for example, files on removable media (CD, DVD),

or on read-only mounted partitions (ntfs, smbfs...),

or simply DON'T want to touch any file from collection for writing...,

why not to have possibility to SEED them?

(other clients have no such trouble.)

maybe i'm wrong?

thanks.

utorrent v.3.0-25053

Linux 32bit :-)

Link to comment
Share on other sites

why not to check permissions for writing NOT BEFORE, but AFTER hash checking,

and if all sums are matched, don't check for writing permission at all?

That issue has been on the list for a while but it hasn't been high enough priority to resolve it yet. I think everyone here agrees that seeding shouldn't require writable data files, so it is recognized as a worthwhile change.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...