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):
• 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)