The download limit is changing all by itself.

[thvet]

I am using Transmission 1.50 (7887) on Ubuntu. I had configured a bandwidth limit of 5 KB/s down and 5Kb/s up (hereafter called "default") and scheduled limits of 30KB/s down and 215kb/s up between 00:00 and 12:00. I have noticed that values for the "default" limit are changing themselves automatically to the values for the scheduled limit. This has happened three times.

After the second occasion I wrote the following shell script:

======================================================

Code: Select all

TORRENT_CONFIG=/home/xxxxx/.config/transmission/settings.json

TIMESTAMP=$(ls -l ${TORRENT_CONFIG} | cut -d' ' -f7)

FILE_DIR=/home/xxxxx/tmp

COPY_FILE=${FILE_DIR}/settings.json-${TIMESTAMP}-$(date '+%Y%m%d%H%M')

cp ${TORRENT_CONFIG} ${COPY_FILE}

[/color]
======================================================
This shell script makes a copy of the file "settings.json". The name of the copy includes the timestamp of "settings.json".

I set up cron to call this script on an hourly basis. Below is the listing of the /home/xxxxx/tmp directory

(Note: I used | sed 's/?????/xxxx/g' to hide the name of my real linux username
===============================================================

Code: Select all

xxxxx@xxxxx-desktop:~/tmp$ ls -ltr
total 104
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-07 15:00 settings.json-13:00-200903071500
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-07 16:00 settings.json-13:00-200903071600
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-07 17:00 settings.json-13:00-200903071700
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-07 18:00 settings.json-13:00-200903071800
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-07 19:00 settings.json-13:00-200903071900
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-07 20:00 settings.json-13:00-200903072000
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-07 21:00 settings.json-13:00-200903072100
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-07 22:00 settings.json-13:00-200903072200
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-07 23:00 settings.json-13:00-200903072300
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 00:00 settings.json-13:00-200903080000
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 01:00 settings.json-13:00-200903080100
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 02:00 settings.json-13:00-200903080200
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 03:00 settings.json-13:00-200903080300
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 04:00 settings.json-13:00-200903080400
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 05:00 settings.json-13:00-200903080500
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 06:00 settings.json-13:00-200903080600
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 07:00 settings.json-13:00-200903080700
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 08:00 settings.json-13:00-200903080800
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 09:00 settings.json-13:00-200903080900
-rw-r--r-- 1 xxxx xxxx 2752 2009-03-08 10:00 settings.json-13:00-200903081000
-rw-r--r-- 1 xxxx xxxx 2755 2009-03-08 11:00 settings.json-10:05-200903081100
-rw-r--r-- 1 xxxx xxxx 2755 2009-03-08 12:00 settings.json-10:05-200903081200
-rw-r--r-- 1 xxxx xxxx 2755 2009-03-08 13:00 settings.json-10:05-200903081300

[/color]
===============================================

You will note that settings.json changed at 10:05 which was the time which I Quit transmission.

From this I have determined that sometimes when I quit Transmission settings.json is updated with corrupt values. I believe that this is a bug which needs to be squatted before the next release of Transmission.