DSM-G600, DNS-3xx and NSA-220 Hack Forum

Update:

I uninstalled the 1.83 nightly and installed 1.82 from your sig, Kylex.  Seems stable so far after 12+ hours of downloading.  That was leaving settings.json alone, by the way.

Hi! I have just tried installing 1.83-1 and 1.83svn. Both have given me a "TRACKER DID NOT RESPOND" error. And after reading that 1.76 still works, I have tried installing it however the same thing happens. Please help.

Last edited by nicholwee (2010-02-17 16:16:00)

Eagerly awaiting 1.90, thankyou for mantaining this KyleK!

CPU utilization on my DNS-321 hasn't gone above 40% since I installed 1.82, whereas with 1.76 I had to keep DHT and PEX turned off otherwise it would stay at 98%.  The web utility would be completely unresponsive under that load. 

I'm a very happy camper so far.  I'm going to be very hesitent to even install 1.90 seeing as how well 1.82 is working for me.  Anyone have a link to new features?

Hope the version 1.90 get compiled soon.. i have not downloaded and uploaded for weeks.. This messed up my ratio.

Last edited by nicholwee (2010-02-19 06:52:09)

Man you guys are impatient
Transmission 1.90 is up and running in the first post of this thread.
It's mainly a bugfix/optimization release, so don't expect anything big.

Let me know if there are problems.

Kylek, thank you for maintain builds for DNS-323.

After installation 1.90 and starting I can see some messages in console about port mappings, torrents saving and so on, looks like debuging info, never such staff in previous versions.

I'll try to reinstall later...

I've experimented a bit with the logging and forgot to fully change it back to the previous version, sorry.

You can either download Transmission-1.90-2.tgz from the first post and update, or simply edit the /ffp/start/transmission.sh.
Change this line:

$su_cmd $user -c "$command -f -g ${TRANSMISSION_HOME} >${TRANSMISSION_HOME}/$name.log &"

to this:

$su_cmd $user -c "$command -f -g ${TRANSMISSION_HOME} >${TRANSMISSION_HOME}/$name.log 2>&1 &"

zuluwalker wrote:

KyleK wrote:

Man you guys are impatient :)
Transmission 1.90 is up and running in the first post of this thread.
It's mainly a bugfix/optimization release, so don't expect anything big.

Let me know if there are problems.

Thanks man, you are dependable as ever! :D

EDIT: Still getting announce errors (tracker did not respond), but now rather than the issue being exhibited on all torrents, it's only happening on a single private tracker. Still, it's better than 1.83 IMHO.

If this still shows up with that particular tracker, could you test if maybe the tracker simply takes a very long time to respond?
Just try a telnet connection with the tracker URL and port. (Do multiple tests, to even the field).

As mentioned in the last comment at http://trac.transmissionbt.com/ticket/2854, the main problem of this ticket was a very overloaded tracker.

Yes, I'm using TransmissionRemoteDotnet  http://code.google.com/p/transmission-remote-dotnet/

Transmission Web Interface shows "Finished" state

Last edited by CadaverousX (2010-02-20 13:39:42)

CadaverousX wrote:

Shall I take the "Finished" state out again?

That would be cool!!! (If it is not difficult for you and for compatibility reasons only)
Because GUI-clients do not understand this status
This leads to an incorrect display of status in the clients written for the standard version of Transmission

Ok, Transmission-1.90-3.tgz is up. It removes the additional "Finished" state for torrents that are stopped and have reached their seed ratio. This should fix your issue with third-party remote clients.

TransmissionBT 1.90-3 works great and fast! Thanks for the speedy compile KyleK!

EDIT: Still getting announce and scrape errors (the infamous "tracker did not respond" response...). It might be with that specific tracker - need to address it personally with the tracker admins.

Last edited by zuluwalker (2010-02-21 07:07:35)