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

OK, since nobody is helping, I helped myself.
Stop Transmission. And begin hacking...
1) If you want transmission daemon to run as it should run - transmission:network, you need to modify following files:
a) /etc/init.d/common
Find following code block:
===========================================
# for process match, some processes need -n, the default, others -x
if test -z "$START_STOP"; then
        START_STOP=-n
fi
===========================================
Add after it following new code block:
===========================================
# do we need to run as different user?
if test -z "$START_USER"; then
        START_USER=root
fi
===========================================
Find following code block:
===========================================
echo -n "Starting $1: "
        start-stop-daemon -S -q -o -x $*
===========================================
Modify it like that:
===========================================
echo -n "Starting $1: "
        start-stop-daemon -S -q -c $START_USER -o -x $*
===========================================
b) /etc/init.d/S81transmission
Find following code block:
===========================================
START_STOP=-x
===========================================
Add after it following new code block:
===========================================
START_USER=$TRANSMISSION_USER:$TRANSMISSION_GROUP
===========================================
c) and final step - modify permissions for transmission.log file
execute: chown transmission:network /var/log/transmission.log
(and chown -R transmission:network /var/lib/transmission)

With START_USER variable you can start any process as  any user  of your choice.

2) Problem with rpc-whitelist can be solved in following way:
In file /etc/init.d/S81transmission find following code block:
==========================================
TRANSMISSION_USER=transmission
TRANSMISSION_GROUP=network
==========================================
Add after it following new code block: (I hope you will put correct IP addresses in place)
==========================================
MY_IP="Your.Work.Subnet.*, Your.Friends.Ip.Address"
==========================================
Go next and find following code block:
==========================================
sed -i -e 's|.*"rpc-whitelist":.*|    "rpc-whitelist": "127.0.0.1,'$network',",|' \
                        "$CONFF/$JSON"
==========================================
Modify it like that:
==========================================
sed -i -e 's|.*"rpc-whitelist":.*|    "rpc-whitelist": "127.0.0.1,'$network','$MY_IP'",|' \
                        "$CONFF/$JSON"
==========================================

3) I think what umask in transmission settings.json file need to be changed to 002,
this allows RW access to files for transmission user and network group.
If you add your users to network group, then you will get full access  to downloaded files.
So change in /var/lib/transmission/settings.json umask value from 18 (dec) on to 2:
"umask": 2,

Thats all folks!
P.S. I am not a linux/unix guru, so no claims accepted.

Last edited by voljka (2011-05-11 01:28:26)

jcard wrote:

"Quite bad setup.": There are 60 possible settings for transmission! Do you really want a GUI with them all?

What you think to be a "must" others might think it  to be a nonsense.
Use a remote client to fully customize transmission, such as 'transgui', or use the command line.

I do not ask GUI. But to initialize over and over same setting make non sense for me in this particular place.
I can agree that this is good to prevent users lockout from transmission management, but there is a place for improvement also.

My English is bad, I know this, so this is not a "must", but IMHO instead.
Never know about "transgui", always used "Transmission Remote GUI", will check first one.
Thank you for answers.

P.S. And I'll be happy to know, what good is to have downloaded files to be read-only and owned by root? If you have a spare time to answer.

Last edited by voljka (2011-05-11 01:17:32)