Transmission

Your hunch is correct, the ppa only has packages for amd64, i386, and lpia.

Thanks for the reply - that version is the one that comes with Jaunty by default. I couldn't find any obvious way to upgrade this, so I added the apt source manually: deb http://ppa.launchpad.net/transmissionbt/ppa/ubuntu jaunty main deb-src http://ppa.launchpad.net/transmissionbt/ppa/ubuntu jaunty...

"You unchoked the peer, but the peer is not interested" means that you offered to upload to the other computer but they didn't want to download from you. It has nothing, directly anyway, to do with your downloading.

Yes you need to compile it yourself.
https://trac.transmissionbt.com/wiki/Building

Delete the files as root.

If you compile with inotify support for the daemon then there is no polling interval.

If you guys are using transmission daemon and have it setup to run as a different user you need to make sure that user has read/write permissions for the files and directories you point it at.

Version 2.03 is available on the usual list: https://forum.transmissionbt.com/viewtopic.php?f=1&t=7612&p=37848#p37848 Changes in this version: Some bugs in the 2.03 distribution were corrected, you can see the changes in the patch files on the Wiki: https://trac.transmissionbt.com/wiki/Buil...

Why Apple is still using HFS+ instead of adopting ZFS or better is beyond me... > Apple can currently just take the ZFS CDDL code and incorporate it > (like they did with DTrace), but it may be that they wanted a "private > license" from Sun (with appropriate technical support and > indem...

What do you consider misleading about the stats?

You know if you guys actually filed bugs these things would probably get fixed faster.

To work around this right now fork your script.

Right now you have to put the -n first in the argument list to make it work, it's a regression that will hopefully be fixed in 2.01

The reason it 'eats' up free memory is because anything a file is read/written, OSX is going to cache it. Try copying some large files from a local hard drive to a external one and see if that 'uses' free memory.

If your system hangs when it's low on free memory and there's plenty of inactive memory lying around unused then there is something else going wrong with it.