Jump to content

µTorrent Server 3.0 alpha build 27079 (for Linux) - x86


Firon

Recommended Posts

v0.380 WIP (2010-11-24)

+ Feature: Auto-refreshing Files list

+ Feature: Auto-refreshing Peers list

The branch I'm working on has a 60 second minimum interval for Files list auto-refresh, simply because it's not exactly that important, and it can potentially be a heavy bandwidth drain (though a refresh can always be forced by clicking the Files tab).

Link to comment
Share on other sites

  • Replies 487
  • Created
  • Last Reply

Top Posters In This Topic

µTorrent Server 3.0 alpha build 25053

WebUI v0.381 (2011-04-30)

After upgrading the kernel to 2.6.32-31 to version 2.6.32-32 average CPU 1.75 1.23 1.45.

The processor temperature as reached 45c ($sensors), although earlier on kernel 2.6.32-31 load was about (0.40 0.49 0.55) and low processor usage was about 37c ($sensors).

One of the engines were deployed at 100%.

Installed the WebUI v0.382 (2011-05-28), the average load on the CPU has dropped 0.33 0.42 0.54

AMD Athlon II X2 260 Processor

Linux hdc1 2.6.32-32-server #62-Ubuntu SMP Wed Apr 20 22:07:43 UTC 2011 x86_64 GNU/Linux

$sensors

CPU1 Temp: +36.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor

CPU2 Temp: +28.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor

Link to comment
Share on other sites

µTorrent Server 3.0 alpha build 25053

WebUI v0.381 (2011-04-30)

After upgrading the kernel to 2.6.32-31 to version 2.6.32-32 average CPU 1.75 1.23 1.45.

The processor temperature as reached 45c ($sensors), although earlier on kernel 2.6.32-31 load was about (0.40 0.49 0.55) and low processor usage was about 37c ($sensors).

One of the engines were deployed at 100%.

Installed the WebUI v0.382 (2011-05-28), the average load on the CPU has dropped 0.33 0.42 0.54

AMD Athlon II X2 260 Processor

Linux hdc1 2.6.32-32-server #62-Ubuntu SMP Wed Apr 20 22:07:43 UTC 2011 x86_64 GNU/Linux

$sensors

CPU1 Temp: +36.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor

CPU2 Temp: +28.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor

For information.

Link to comment
Share on other sites

Wow' date=' you need glibc 2.11 minimum with the new version? If there is anything I don't touch in my Linux server, glibc is going to be high on the list.[/quote']

This excludes me from using it as well, at least until CentOS updates to 6.0, which uses glibc 2.12. Is there a specific reason why this is being compiled with library requirements that aren't supported by many stable server distributions? Limiting the user base to cutting edge desktop distributions seems to be short-sighted.

Joined the forum just to agree to this, hopefully the dev's are reading. If there is any way to get utorrent running outside of glibc2.12 (I.E. CentOS) I'll use it, otherwise, I'll have to continue to run the old version.

*edit* I just saw the post of future versions supporting this. Thanks for the great work, waiting _somewhat_ patiently :)

Thanks.

Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...

Read the 1st post, it's explained:

For trackers who whitelist, the user agent is uTorrent/300B(build#)(server)

The peerid is identical to the Windows 3.0 client. They share version numbers because of a common codebase.

So ask tracker teams to allow this client.

Link to comment
Share on other sites

Read the 1st post, it's explained:

So ask tracker teams to allow this client.

Hi moogly,

Thanks for that, I'll request it.

My initial question was more along the line of "Is it possible to somehow check that via the CLI?"

I installed the server some time ago and couldn't seem to find it via a command like ./utserver --version

Link to comment
Share on other sites

I installed the server some time ago and couldn't seem to find it via a command like ./utserver --version

To find the build version, you can do this:

utorrent@ubuntu:~/utorrent-server-v3_0$ ./utserver -usage

server started - using locale fr_FR.UTF-8

300B (25376) 2011-06-10 17:49:03 -0700

Usage: utserver -settingspath -logfile -configfile -pidfile -daemon -usage

settingspath - location of settings directory

logfile - location and name of log file

configfile - location and name of configuration file

pidfile - location and name of file to contain process ID

daemon - run process as a daemon

usage - print this message and exit

server exited with 0

Link to comment
Share on other sites

  • 2 weeks later...

Archived

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

Guest
This topic is now closed to further replies.

×
×
  • Create New...