ClearFoundation

Sorted that and it now works. Thanks once again for taking the time

OK, since this thread has become active again, I've changed my version of the start-up script to better detect if transmission is already running and then give you a more friendly error message. I've also changed how it detects the PID of the running task and I've broadened the stop command to kill the first instance of transmission-daemon it comes across. Now if you (accidentally) have more than one instance of transmission running a repeated "service transmission-daemon stop" will eventually kill all the instances of it.

For your access problem, the relevant bit of my settings.json is:

Mine is similar to yours was, Duncan, but without the "rpc-username" being set. I still have "rpc-whitelist-enabled": true,"

My connection to ISP very often disconnects, and Transmission after that stay like stopped very long time until I manual re-announced my downloads.
Maybe somebody know how create automatic announce?

The problem has been solved after installing new version of Transmission 1.91+
source build.transmissionbt.com/job/trunk-linux/ or you can wait Transmission 1.92!
More details you can read here
forum.transmissionbt.com/viewtopic.php?f=1&t=9700

@bartsidee

Have a look at an issue I've had with the installation in this thread.

It looks like COS is expecting libcurl.so.4 to be a symlink to libcurl.so.4.0.0 rather than the proper file. It has thrown messages during the last couple of COS updates (although it has not broken anything that I've noticed).

Can I suggest you change the lines:

to

@ Nick Howit

Can you tell me what are the differences between your startup script and the original one posted in the how-to. In other words what script should i use?

You can use either, but to use the original one you need to install the start stop daemon which is from a debian distro. As COS is not a debian based distro, I hacked the original script to use features native to COS/RHEL/Fedora. This means you can skip bartsidee's stage which installs the start stop daemon.

I am biased, but I would give mine a go first as it avoids the extra package installation (which, according to his post, does not install cleanly). If there are any problems with it please post back.

Thanks for your fast reply!

Nick Howitt wrote:
I've edited my start-up script again.

Change:

Code:

ps -fe | grep $DAEMON | head -n1 | cut -d" " -f 6 > ${PIDFILE}

to

Code:

ps -fe | grep $DAEMON | head -n1 | awk '{print $2}' > ${PIDFILE}

The original code snippet I found in the internet was failing if the process ID was only 4 digits long.

Is this already changed in your script?

I changed it again since then. The second way is fine, but I now use:
which is much prettier.

I updated the code I originally posted each time I made a modification to it so it always contains the latest version. Unless someone finds a problem with it (or updates the /etc/init.d/functions script where I stumbled on what I thought was an irritating bug), I don't anticipate another change.

Hi everyone,

It took one small patch to "downgrade" the curl version, but I managed to build the ClearOS transmission RPM! I have attached a screenshot of it running on one of the development systems. Next steps:

- Nick: could you confirm that the startup script is up-to-date? I'll add it to the RPM.
- Add the package to the new build system (maybe)

This is a personal project of mine and it will be part of the "community" packages that will be available in ClearOS 5.2.