NSLU2-Linux
view · edit · print · history

Optware.Clutch History

Hide minor edits - Show changes to markup

February 07, 2009, at 08:25 AM by axm -- deleted: obsolete
Changed lines 1-51 from:

this article is a mess. an actual transmission/ clutch howto for nslu2 it is really appreciated.

Yes, this is not a step-by-step-execute-this-line tutorial - Feel free to improve, but at least with the packages I got my hands on a lot had to be changed. And I would wait for a stable release to do a repackaging or an install script.
  • For running clutch/transmission as non-root (Unslung 6.10 / May 2008 / recently bought nslu2 / transmission 1.11 / clutch 0.4-3):
  • Note that running as root is probably a lot easier, maybe even runs out of the box (just make sure socket and pid file match).
  • ipkg install transmission lighttpd php php-fcgi clutch
  • transmission is incompatible with the "torrent" packages (seems to be a successor)
  • Configure lighttpd (/opt/etc/lighttpd/lighttpd.conf), setting the user as desired and starting it as root is sufficient. Uncomment the line for enabling "mod_fastcgi". The clutch directory (/opt/etc/share/www/lighttpd/clutch) still has to be reachable somehow of course, links should be sufficient.
  • Configure clutch (/opt/etc/clutch.conf) and transmission (/opt/etc/transmission.conf) paths to your liking, with a matching pid file name.
  • NOTE: clutch makes so many assumptions, configuring the two parameters in /opt/etc/clutch.conf is propably more impractical than just editing S88clutch directly, but I have not tested if there are more dependencies on it.
  • The transmission pid directory does not seem to be created automatically, so do that (do not know about the socked directory, created that as well).
  • The S88clutch is the script that will start the transmission-daemon handling the actual work.
  • In my case, adding -g /opt/etc to the transmission-daemon startup was necessary, so that the /opt/etc/transmission.conf was actually used. But this parameter also distinguishes, where the work directories for downloading will be, so set it to /home/username or something and ln -s /opt/etc/transmission.conf /home/username/transmission.conf. Otherwise there will be problems, I even hat /etc/init.d as download directory.
  • Also, I have not found a way to set the socket file in the config file, so I added -s /path/to/socket to the startup as well.
  • See below for all changes to the startup line.
  • Add -f (foreground) to the startup for testing, otherwise it is pretty silent, with it missing rights are easily spotted.
  • This will at least include the socket file (and the directories leading to it) in clutch/remote.
  • Since I had previous attempts, running transmission as root, there were a couple of directories more I had to give permissions to as well. Since I did not know, what they were generally for, I created a new group, made my torrent user a member, chown root:newgroup xxx, and added group rights.
  • Executing S88clutch now should produce sth like: "Starting transmission-daemon, Transmission 1.11+ (5740) started"
  • Check (with -f: ctrl-z to pause the process, fg to restart it, bg would put it in background) that the pid and socket files are actually generated!
  • The web gui now might report "transmission-daemon does not appear to be running" or "Could not connect to the server. You may need to reload the page to reconnect." if the file specified in /opt/share/www/lighttpd/clutch/remote/data/socket.txt (done by the S88clutch script based on /opt/etc/clutch.conf HOME) cannot be found or clutch cannot find the pid file. Also make sure, cgi is enabled in lighttpd.
  • If everything worked fine, by now there should be buttons to add torrents on the webinterface which should start downloading immediately. As soon as the first data arrives, a permission denied error might occur, use -f to check for lack of permission.
  • After that, it should actually be downloading. Removing a download does not affect the actual files.
  • no watching of torrent-input directory, no completion moving yet
  • Changing the Listener port (it is set in the ui - lower left corner - to 51413 by default - the one in the conf file is ignored) does not work. I could only get incoming connections (portforwarded correctly) with the default port. Sites for testing connectivity reported success falsely, this might have been ghost processes, but I am not sure. So the feature about changing the port is a plain lie to until I am proven wrong ;)

______

finishing:

do not remove the -f option, but use it for a logging workaround:

        /opt/bin/transmission-daemon -f -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} \
           -g ${HOME} >> ${HOME}/.transmission/log/manual_log 2>&1 &

startup: /etc/init.d/S88clutch:

  1. !/bin/sh

/opt/etc/init.d/S80lighttpd $* su username -c "/opt/etc/init.d/S88clutch $*"

and for stopping:

ln -s /etc/init.d/S88clutch /etc/init.d/K88clutch

.. should take care of automatic starting/stopping (the init.d should be called by rc.d/rc.optware, but I have not tested it)

to:

The previous manual is not necessary anymore, clutch comes automatically with the transmission packages. As the older transmission packages are no longer usable, I remove the mess I made.

June 21, 2008, at 09:19 AM by axm --
Changed lines 2-3 from:

- Yes, this is not a step-by-step-execute-this-line tutorial - Feel free to improve, but at least with the packages I got my hands on a lot had to be changed. And I would wait for a stable release to do a repackaging or an install script.

to:
Yes, this is not a step-by-step-execute-this-line tutorial - Feel free to improve, but at least with the packages I got my hands on a lot had to be changed. And I would wait for a stable release to do a repackaging or an install script.
June 21, 2008, at 09:18 AM by axm -- yes - the transmission.conf path was incorrect. hope it helped anybody to get it running.
Changed lines 2-3 from:
to:

- Yes, this is not a step-by-step-execute-this-line tutorial - Feel free to improve, but at least with the packages I got my hands on a lot had to be changed. And I would wait for a stable release to do a repackaging or an install script.

Changed lines 10-13 from:
  • Configure clutch (/opt/etc/clutch.conf) and transmission (/opt/etc/init.d/transmission.conf) paths to your liking, with a matching pid file name.
  • question - is the above path right? mine is at /opt/etc/transmission.conf
to:
  • Configure clutch (/opt/etc/clutch.conf) and transmission (/opt/etc/transmission.conf) paths to your liking, with a matching pid file name.
June 17, 2008, at 11:53 PM by ls --
Changed lines 1-2 from:

this article is a mess, an actual transmission/ clutch howto for nslu2 it is really appreciated.

to:

this article is a mess. an actual transmission/ clutch howto for nslu2 it is really appreciated.

June 17, 2008, at 11:52 PM by ls -- request for clarity
Changed lines 1-3 from:
  • For running clutch/transmission as non-root (Unslung 6.10 / May 2008 / recently bought nslu2 / transmission 1.11 / clutch 0.4-3):
to:

this article is a mess, an actual transmission/ clutch howto for nslu2 it is really appreciated.

  • For running clutch/transmission as non-root (Unslung 6.10 / May 2008 / recently bought nslu2 / transmission 1.11 / clutch 0.4-3):
June 08, 2008, at 05:42 AM by au -- error in path
Added lines 8-10:
  • question - is the above path right? mine is at /opt/etc/transmission.conf
May 11, 2008, at 09:38 AM by axm --
Changed line 27 from:
  • Changing the Listener port (it is set in the ui - lower left corner - to 51413 by default) does not work. I could only get incoming connections (portforwarded correctly) with the default port. Sites for testing connectivity reported success falsely, this might have been ghost processes, but I am not sure. So the feature about changing the port is a plain lie to until I am proven wrong ;)
to:
  • Changing the Listener port (it is set in the ui - lower left corner - to 51413 by default - the one in the conf file is ignored) does not work. I could only get incoming connections (portforwarded correctly) with the default port. Sites for testing connectivity reported success falsely, this might have been ghost processes, but I am not sure. So the feature about changing the port is a plain lie to until I am proven wrong ;)
May 11, 2008, at 09:37 AM by axm -- port howto
Added lines 26-27:
  • Changing the Listener port (it is set in the ui - lower left corner - to 51413 by default) does not work. I could only get incoming connections (portforwarded correctly) with the default port. Sites for testing connectivity reported success falsely, this might have been ghost processes, but I am not sure. So the feature about changing the port is a plain lie to until I am proven wrong ;)
May 10, 2008, at 08:53 PM by axm --
Changed line 31 from:
        /opt/bin/transmission-daemon -f -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} \\\\
to:
        /opt/bin/transmission-daemon -f -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} \
May 10, 2008, at 08:48 PM by axm --
Changed line 31 from:
        /opt/bin/transmission-daemon -f -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} \\
to:
        /opt/bin/transmission-daemon -f -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} \\\\
May 10, 2008, at 08:48 PM by axm --
Changed line 31 from:
        /opt/bin/transmission-daemon -f -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} \
to:
        /opt/bin/transmission-daemon -f -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} \\
May 10, 2008, at 08:47 PM by axm -- added logging
Changed lines 13-14 from:
  • Also, I have not found a way to set the socket file in the config, so I added -s /path/to/socket to the startup as well.
  • all changes in S88clutch: /opt/bin/transmission-daemon -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} -g /home/username
to:
  • Also, I have not found a way to set the socket file in the config file, so I added -s /path/to/socket to the startup as well.
  • See below for all changes to the startup line.
Changed lines 29-30 from:

remove -f in /opt/etc/init.d/S88clutch

to:

do not remove the -f option, but use it for a logging workaround:

        /opt/bin/transmission-daemon -f -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE}            -g ${HOME} >> ${HOME}/.transmission/log/manual_log 2>&1 &
May 10, 2008, at 07:03 PM by axm -- adjusting some configuration errors
Changed line 12 from:
  • In my case, adding -g /opt/etc to the transmission-daemon startup was necessary, so that the /opt/etc/transmission.conf was actually used.
to:
  • In my case, adding -g /opt/etc to the transmission-daemon startup was necessary, so that the /opt/etc/transmission.conf was actually used. But this parameter also distinguishes, where the work directories for downloading will be, so set it to /home/username or something and ln -s /opt/etc/transmission.conf /home/username/transmission.conf. Otherwise there will be problems, I even hat /etc/init.d as download directory.
Changed line 14 from:
  • all changes in S88clutch: /opt/bin/transmission-daemon -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} -g /opt/etc
to:
  • all changes in S88clutch: /opt/bin/transmission-daemon -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} -g /home/username
Changed lines 23-35 from:
  • If everything worked fine, by now there should be buttons to add torrents on the webinterface which should start downloading immediately. As soon as the first data arrives, a permission denied error will occur.
  • With the -f parameter enabled, transmission will reveal its ugly assumptions about where it should be writing data to. I havent found any place to configure these paths, please (PLEASE!) correct me. These paths include:

/opt/etc/daemon /opt/etc/resume /opt/etc/stats.benc /opt/etc/torrents /etc/init.d (the downloaded data is actually stored here! wtf?)

  • At this point, it should actually be downloading. Removing a download does not affect the actual files.
  • the directories to be configured in transmission.conf seem to be ignored as well.
  • no completion moving
to:
  • If everything worked fine, by now there should be buttons to add torrents on the webinterface which should start downloading immediately. As soon as the first data arrives, a permission denied error might occur, use -f to check for lack of permission.
  • After that, it should actually be downloading. Removing a download does not affect the actual files.
  • no watching of torrent-input directory, no completion moving yet
May 10, 2008, at 05:39 PM by axm --
Added line 2:
  • Note that running as root is probably a lot easier, maybe even runs out of the box (just make sure socket and pid file match).
Added line 26:
Changed lines 36-37 from:

____

to:

______

Changed lines 41-42 from:

startup: /etc/init.d/S88clutch

to:

startup: /etc/init.d/S88clutch:

Changed lines 46-47 from:

<--

to:

and for stopping:

May 10, 2008, at 05:35 PM by axm -- Adding clutch howto
Added lines 1-48:
  • For running clutch/transmission as non-root (Unslung 6.10 / May 2008 / recently bought nslu2 / transmission 1.11 / clutch 0.4-3):
  • ipkg install transmission lighttpd php php-fcgi clutch
  • transmission is incompatible with the "torrent" packages (seems to be a successor)
  • Configure lighttpd (/opt/etc/lighttpd/lighttpd.conf), setting the user as desired and starting it as root is sufficient. Uncomment the line for enabling "mod_fastcgi". The clutch directory (/opt/etc/share/www/lighttpd/clutch) still has to be reachable somehow of course, links should be sufficient.
  • Configure clutch (/opt/etc/clutch.conf) and transmission (/opt/etc/init.d/transmission.conf) paths to your liking, with a matching pid file name.
  • NOTE: clutch makes so many assumptions, configuring the two parameters in /opt/etc/clutch.conf is propably more impractical than just editing S88clutch directly, but I have not tested if there are more dependencies on it.
  • The transmission pid directory does not seem to be created automatically, so do that (do not know about the socked directory, created that as well).
  • The S88clutch is the script that will start the transmission-daemon handling the actual work.
  • In my case, adding -g /opt/etc to the transmission-daemon startup was necessary, so that the /opt/etc/transmission.conf was actually used.
  • Also, I have not found a way to set the socket file in the config, so I added -s /path/to/socket to the startup as well.
  • all changes in S88clutch: /opt/bin/transmission-daemon -s "${HOME}/.transmission/daemon/socket" -p ${PIDFILE} -g /opt/etc
  • Add -f (foreground) to the startup for testing, otherwise it is pretty silent, with it missing rights are easily spotted.
  • This will at least include the socket file (and the directories leading to it) in clutch/remote.
  • Since I had previous attempts, running transmission as root, there were a couple of directories more I had to give permissions to as well. Since I did not know, what they were generally for, I created a new group, made my torrent user a member, chown root:newgroup xxx, and added group rights.
  • Executing S88clutch now should produce sth like: "Starting transmission-daemon, Transmission 1.11+ (5740) started"
  • Check (with -f: ctrl-z to pause the process, fg to restart it, bg would put it in background) that the pid and socket files are actually generated!
  • The web gui now might report "transmission-daemon does not appear to be running" or "Could not connect to the server. You may need to reload the page to reconnect." if the file specified in /opt/share/www/lighttpd/clutch/remote/data/socket.txt (done by the S88clutch script based on /opt/etc/clutch.conf HOME) cannot be found or clutch cannot find the pid file. Also make sure, cgi is enabled in lighttpd.
  • If everything worked fine, by now there should be buttons to add torrents on the webinterface which should start downloading immediately. As soon as the first data arrives, a permission denied error will occur.
  • With the -f parameter enabled, transmission will reveal its ugly assumptions about where it should be writing data to. I havent found any place to configure these paths, please (PLEASE!) correct me. These paths include:

/opt/etc/daemon /opt/etc/resume /opt/etc/stats.benc /opt/etc/torrents /etc/init.d (the downloaded data is actually stored here! wtf?)

  • At this point, it should actually be downloading. Removing a download does not affect the actual files.
  • the directories to be configured in transmission.conf seem to be ignored as well.
  • no completion moving

____

finishing: remove -f in /opt/etc/init.d/S88clutch

startup: /etc/init.d/S88clutch

  1. !/bin/sh

/opt/etc/init.d/S80lighttpd $* su username -c "/opt/etc/init.d/S88clutch $*" <--

ln -s /etc/init.d/S88clutch /etc/init.d/K88clutch

.. should take care of automatic starting/stopping (the init.d should be called by rc.d/rc.optware, but I have not tested it)

view · edit · print · history · Last edited by axm.
Based on work by axm, ls, and au.
Originally by axm.
Page last modified on February 07, 2009, at 08:25 AM