mcdonald

You need to set these up in the configuration file. Search for 'dir_download' in the manual.

The "alpha"-ness of uTorrent Server isn't because it is a bunch of new, untested code. It is derived from a branch that has had other GUI-less products built and released out of it, and those products have been running very well in production for months. The "alpha"-ness is more because we are working on making it a server with the functionality people expect from daemonizable Linux executables. Some of those features will be available probably by the end of the week as long as the stress test doesn't turn up anything (it hasn't so far). I'm trying to keep releases stable so I'm doing a fair amount of testing before releasing since people running servers expect to have high levels of uptime. The upcoming release will be based on a more recent branch, so it will include some uTP fixes/improvements among other changes.

Are you running on a 64-bit LInux? That could be a problem. What is a "vps"?

See http://forum.utorrent.com/viewtopic.php?id=83630

Thanks for the report. I've been building the server product on a stable code line branch, but one that is a few months behind the code line trunk. A couple of days ago, there was a point at which the frequently-unstable development trunk was stable (according to results of automated unit and system testing), so I created another branch from it. The new branch should have better handling of unavailable mounts (as long as the OS recognizes the mounts are unavailable). I expect to be releasing from that new branch pretty soon since it has been testing consistently well, although I'll first conduct a week-long stress test to see how the server built from the new branch performs under heavy load. What were the memory usages you were seeing with other products (if any) under the same conditions?

It's likely to be OK. I'm running Ubuntu desktop 10.04 LTS i386 on two workstations I use to develop and test the product. Nightly builds (including the ones released) are built and tested on an Ubuntu 9.10 image.

You need to include a colon between the setting name and its value.

There's a bug in the docs - the docs say to use a forward slash when specifying the LOGFILE argument (as in /LOGFILE) - the docs should say to use a dash (as in -LOGFILE).