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

For convenience I uploaded a new version that includes most of DFreeze changes but keeps the rest of the script (especially the directories the same).  I did not enable the Uploading / Seeding as active connections however.  I updated my original posting with the new filename, but in case you can't be bothered:

wget http://pellcorp.com/dns323/trans14_utils.tar.gz
tar -zxvf trans14_utils.tar.gz -C /

This script does require /ffp/start/syslog.sh to be active to get the logs.  For the moment they are being sent to /var/log/messages and RimBlock is correct in that you will lose any logs if you restart.  What I have done in the past (and it kind of works) is on startup delete the /var/log/messages and create a soft link to /ffp/var/log/messages instead.

It works until the /var/log/messages rolls over.

Potentially you might be able to completely remove the /var/log/ directory on startup and create a soft link to /ffp/var/log/ - but I have not tried that.

WARNING - I DON'T TRULY UNDERSTAND THE IMPACT OF DOING THIS SO BE CAREFUL!!!!!

A couple of extra things I did once off (not sure any of it was necessary other than lastlog, wtmp and btmp).

cp -r /var/log/samba /ffp/var/log
cp -r /var/log/glusterfs /ffp/var/log
cp -r /var/log/cores /ffp/var/log
cp /var/log/lastlog /ffp/var/log
cp /var/log/wtmp /ffp/var/wtmp
cp /var/log/btmp /ffp/var/btmp

I only had to do this once to quiet some errors in /ffp/var/log/messages

I don't believe /var/log/messages gets written to without syslog, so no need to do anything with that, can just append to /ffp/var/log/ one once you remove /var/log and create soft link.

Cheers
Jason

It`s possible to rewrite this useful script without using bash? I have not bash installed and don`t plan to. Please

Well with two days leave and having to sit at home I have got my DNS 323 working again (although one drive is reporting io errors on copying files across)

I have therefore spent most of yesterday updating the script to work with Transmission 1.40+ and doing some testing.

There are a few original bugs removed, probabily a few new ones added :-).

The script installs in to the .transmission-daemon set of directories.
scripts - main script
logs - script logs
archive - archiving .torrent files (not yet implemented)
working - transmission working directory to help split the running and completed torrents.

There are two directories on the main share point (usually /mnt/HD_a2).
completed - For all completed and seeded to specified ratio torrents.
watch - location for new .torrent files and for putting the 'cycle' file to prompt a cycling of the scripts before the full wait period.

The script is started automatically from the /ffp/start directory.

If you change any of the directory names then you will need to do so in the install and the main script.  I will look at having the install script directory names automatically set in the main script at some point.

The script requires nothing more than ffp 0.5 and Transmission 1.40+ to be installed.

It does need some 'field testing' so anyone who is interested please downlod and feedback here.

I will upload it to http://dns323.thecorewithin.net/

It will be named trans_utils-0.2.tgz

Regards
RB

I installed the script and it seems to work except if I set QUIT_TRANSMISSION_WHEN_INACTIVE=1. If it is set to 1, transmission does not seems to restart properly when a new torrent file is added to the watch directory.

A newbie question. Why the script looks for a "cycle now" file instead just to check if watch directoy has something? If it looks for any file, it will save us the trouble of create a "cycle now" file and deposit it there at the same time we drop a torrent file in.

ADDED on Dec 25:
Found the following in .transmission-daemon\logs\transmission-utilities.log

[Thu Dec 25 07:22:01 GMT 2008]  Starting set bandwidth.
[Thu Dec 25 07:22:01 GMT 2008]  Transmission state file not found.
[Thu Dec 25 07:22:01 GMT 2008]  No items found in SCHED_TIME. Not setting bandwidth allocation.
[Thu Dec 25 07:22:01 GMT 2008]  Finished set bandwidth.

Maybe the issue is because I don't have $TRANSMISSION_HOME/daemon/state for my installation.

This is the same for transmission 1.40 and 1.42.
Thanks.

EDITED on Dec 28:
Found the reason why trans_utils is not able to re-start transmssion...
When checking if transssmion is running, the statement
TRANSMISSION_IS_RUNNING=`ps -A | grep -v grep | grep transmission-d | wc -l` is used, but it will always return positive because trans_utils is running off ./transmission-deamon/script.

By changing it to
TRANSMISSION_IS_RUNNING=`ps -A | grep -v grep | grep bin/transmission-d | wc -l`

Transmission will re-start when a new torrent is added to the watch directory.

Last edited by toolbox (2008-12-29 04:12:18)

Ok,

The "No items found in SCHED_TIME. Not setting bandwidth allocation." message should read "No items found in SCHEDULE_ENTRIES variable.  Not setting bandwidth allocation."

Does the $SCHEDULE_ENTRIES variable have any values set at the top of the script and if so can you please paste a copy here ?.  I have corrected the error message to reflect SCHEDULE_ENTRIES and not SCHEDULE_ITEMS as the variable name.

I have added check for the CYCLE_FILE not being set and to sysle if any file then appears in the watch directory.
I have changed the 'ps' check as suggested.
I have added a couple more comments so evey function has at least one line for description.

Still to do;

Max concurrent processes code to be checked.
Find alternative to the old state file for bandwidth currently set.
Implement the logging severity so not all messages are logged if the user wishes.
Housekeeping for the log files
Possible e-mail alerts for new torrents added, new torrents completed (seeding) and torrents removed (seeding ration reached).  This depends on any installed email server on the DNS-323 as standard.  I believe there is but need to check and find out what it is.

I need to debug these changes before repackaging and cannot do that from work so will package up after a bit of testing tonight (hopefully).

Regards
RB

Hi Toolbox,

Ok, I take it you are meaning that the utils script is checking to see if Transmission is up and running before Transmission has had a chance to fully start up after a reboot.

Ok first thought then would be to introduce a three strikes wait cycle.

I can get the script to try once and if it gets no response then it will wait for a user specified time period (i.e. 1 minute) and then try again.  Thae script will do this 3 times before reporting a problem.  I don't think there is an option to find out if Transmission has fully started up.

That sould get round the issue.

RB

Thanks Toolbox.

I will continue with Transmission for now as it does what I need and I am never in too much of a rush for downloads.

I have 250+ dvd's to rip so uShare can stream them for my XBox360.  i can then store them all in boxes.  This as you can imagine will take some time so script is not such high priority at the moment.

Regards
RB

i was also wondering, how can i change the queue list priority ?

Last edited by heema (2009-01-03 21:02:09)

RimBlock. THis script is great! Thanks.

After I changed the Transmission boot script from nobody to my own user name (to be better able to manage downloaded files from Windows/Samba using an account set up with the DNS utilities), the trans_utils boot script stopped working... nohup.out said  "torrent_utils.sh: applet not found". I tried deleting and rerunning the install script but the same error came again. In my experiments, I also realized that I needed to run the boot script as my own user name as I had to chown to the .transmission-daemon directory for the first change.

What I came up with was :         su jmcqup -c "$TRAN_UTILS/$util_command &" in line 13.

Could you advise if my feeble-minded effort is likely to cause problems. At the moment it seems to work, but maybe a little less stable.

cheers

Have the changes outlined by heema above been made to v0.2 of the script?
I recently upgraded from Transmission 1.22 to 1.51, the jump means i need to use a new script. My ISP has peak and off-peak so i have to schedule my bandwidth.

Many thanks to the script author too, not something i could have done myself.

heema wrote:

thanks for the script and it works great

but i had to change in /ffp/start/trans_utils.sh
TO_KILL=`ps -a | grep $util_command | grep -v grep | cut -d' ' -f2`
to
TO_KILL=`ps -a | grep $util_command | grep -v grep | cut -d' ' -f1`

to be able to stop the script

I was looking for this.
After editing the file now it can be stopped.

Thanks.



[UPDATE]

Okay, how to uninstall or revert this hack?
I can't make it to work.

I want to stop or restart and for both I get this error:
root@dlink-0A78F3:/mnt/HD_a2# /ffp/start/trans_utils.sh restart
Usage: /ffp/start/trans_utils.sh start|stop|restart|status

root@dlink-0A78F3:/mnt/HD_a2# /ffp/start/trans_utils.sh stop
Usage: /ffp/start/trans_utils.sh start|stop|restart|status

So, after edit the files and changed f2 -> f1, the file can be stopped.

Then, I put a torrent in the watch folder to test if it is working but then nothing happened.
Torrent has been added into watch folder and transmission did not show any downloads.

I tried tyoing this into ssh
root@dlink-0A78F3:/mnt/HD_a2# transmission-remote -l
[21:44:04.242] JSON parser failed at line 1, column 1: "<h1>401: Unautho"
[21:44:04.243] transmission-remote: Unable to parse response "<h1>401: Unauthorized</h1>Unauthorized User"

Can anyone help?

Last edited by nyunyu (2009-05-06 17:22:47)