" chmod o+w /shares/internal/BT/*.*"

then my transmission.sh is like this:
________________
#!/bin/sh
#
# Copyright (C) 2007 JRM
#
# Starts or stops the transmission daemons.
# Writes directory permissions and changes owner for
# the transmission.socket.

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/bin:/opt/
NAME="Transmission"
DESC="torrent daemon"

case "$1" in
start)
echo -n "Starting $DESC: "
transmission-daemon -s /tmp/transmission.socket
echo "$NAME."
sleep 2
chmod -R 777 /tmp/transmission.socket
chown -R www-data:www-data /tmp/transmission.socket
sleep 2
transmission-remote -f /shares/internal/DOWNLOADS/
sleep 1 ps aux | grep transmission-daemon
;;
stop)
echo -n "Stopping $DESC: "
killall transmission-daemon
echo "$NAME."
;;
chmod o+w /shares/internal/BT/*.*
N=/etc/init.d/$NAME
echo "Use: $N {start|stop}" >&2
exit 1
;;
esac
exit 0
____________________

this repair permissions in BT (in your drive BT) directory each time that you start Transmission like when you stop and start the MBWE drive by the rings buttom. It's not perfect, but work.

I've been following the advice in this forum but I still couldn't make clutch and transmission work together. I have the following versions:

Transmission-1.20
Clutch 0.4

I am able to get the Clutch web page and open a torrent file for download, but after a minute, I receive the dreaded "Connection Failed" message. The error log indicates a socket connection issue. I have changed Clutch/remote/data/socket.txt to point to /tmp/transmission.socket and got the same error, then tried to point it to /root/.config/transmission/daemon/socket and received the same thing. Once I get this message, I have to remove the directory /root/.config/transmission and recreate it. Otherwise, transmission-daemon will not run.

The text below is what I received from http://myBookIP/Clutch/remote/?action=requestSettings&param=0&filter=all&sort_method=queue_order&sort_direction=ascending&search=

"This program has encountered an error and will now exit."

Here's how I run transmission:
1. transmission-daemon -s /tmp/transmission.socket
2. chmod 777 /tmp/transmission.socket
3. chmod 777 -R /remote/.config/transmission
4. ln -s /tmp/transmission.socket /root/.config/transmission/daemon/socket

transmission-daemon seems to be stable. But, when I get to running Clutch web interface and try to download a torrent, transmission-daemon processes defunct. This leaves transmission-daemon unable to start properly until I recreate /root/.config/transmission/daemon.

I have recompiled my php, openssl, pkg-config, and transmission (with the necessary options). But I still get the same error.

I'm hoping that somebody can help so I can finally make clutch and transmission working together.

I logged in again and somehow ldconfig did it. Funny but I think I executed the command once earlier.. but anyway..now the daemon is up…

I have also tried to add the lib dir to /etc/ld.so.conf - but /opt/lib is already there

So did you run ldconfig?

I believe that libintl comes as part of gettext so if you don't have it yet try installing that.

 ipkg install gettext 

I am a linux-newbee who has been trying to install transmission following this guide: http://kyyhkynen.net/stuff/mybook/torrent_intro.php

1. su
2. installed optware follow the guide on the wikidot pages.
3. installed nano without problems
4. then did

1. /opt/bin/ipkg install transmission libiconv

5. created dirs for transmission (following guide) :

1. mkdir ~/.config
2. mkdir ~/.config/transmission

but the my trouble starts:
when I try to start the daemon I get this:

1. /opt/bin/transmission-daemon

/opt/bin/transmission-daemon: can't load library 'libintl.so.3'

I can find the library in /opt/lib - but it points to another lib : libintl.so.3 -> libintl.so.3.4.3
which is present i the dir.

I have also tried to add the lib dir to /etc/ld.so.conf - but /opt/lib is already there

Anybody - any Ideas ?

Kind regards
Anders Raabo

I have Transmission & Clutch working great for the most part. My problems are, I cannot delete something that transmission downloaded without connecthing via SSH and using su - to get root access. How can I make it so I can delete the files from my mapped drive? Second, for some reason even though I have configured my save path as /shares/internal/BT it still saves to / every once and a while. Anyone have some suggestions on this?

 transmission-daemon -s /tmp/transmission.socket cd /usr/www/lib/clutch/remote/data nano socket.txt 

Insert the transmission socket path

 /tmp/transmission-socket 

Chmod dirs again

 chmod -R 777 /tmp chmod -R 777 /usr/www/lib/clutch/remote/data 

and now everything seems to work fine! ^___^

maybe it's time to make an updated version of the howto since

1. php and open ssl failed to compile in my MBWE 500Gb so I had to install them via optware (way easier!)

2. latest version of transmission (at least the one in optware) use different path (/root/.config/transmission instead of /root/.transmission)

3. I had to edit lighttpd to use clutch (you can find an already modified one here

4. the howto miss the part about chmod after starting transmission-daemon

FYI there's another howto here that use optware instead of compiling (but has same problem of the official one)

Remember when you originally linked it, you were in /root/.transmission not /root/.config/transmission.

 # transmission-daemon -s /tmp/transmission-socket # transmission-remote -f /shares/internal/PUBLIC/ transmission-remote: failed to connect to socket file: /root/.config/transmission/daemon/socket: No such file or directory 

and

 # ps aux | grep transmission-daemon root 16913 0.0 3.9 3984 1192 ? S 19:32 0:00 transmission-daemon -s /tmp/transmission-socket root 16914 0.0 3.9 3984 1192 ? S 19:32 0:00 transmission-daemon -s /tmp/transmission-socket root 16915 0.0 3.9 3984 1192 ? S 19:32 0:00 transmission-daemon -s /tmp/transmission-socket root 17120 0.0 0.9 656 300 pts/0 S+ 20:58 0:00 grep transmission-daemon 

How do I know that it isn't running? because the socket file is only created while the daemon is running.

Start the daemon with:

 transmission-daemon -s /tmp/transmission-socket 

but seems I still have problem

 # ln -s /tmp/transmission-socket socket # ls -l total 16 drwxr-xr-x 2 root root 4096 Apr 21 19:32 blocklists drwxr-xr-x 2 root root 4096 Apr 21 19:32 daemon drwxr-xr-x 2 root root 4096 Apr 21 19:32 resume lrwxrwxrwx 1 root root 24 Apr 21 19:36 socket -> /tmp/transmission-socket drwxr-xr-x 2 root root 4096 Apr 21 19:32 torrents # transmission-remote -f /shares/internal/PUBLIC/ transmission-remote: failed to connect to socket file: /root/.config/transmission/daemon/socket: No such file or directory 

what I'm missing now?

 # transmission-daemon -s /tmp/transmission-socket 

 # cd /root/.transmission/daemon 

note that the command

 # ps auxww | grep transmission 

In file included from bencode.c:38:
utils.h:44:23: libintl.h: No such file or directory
bencode.c: In function ‘bencWalk’:
bencode.c:672: warning: implicit declaration of function ‘gettext’
make[2]: * [bencode.o] Error 1
make[2]: Leaving directory ‘/tmp/myfiles/transmission-1.11/libtransmission’
make[1]: * [all] Error 2
make[1]: Leaving directory ‘/tmp/myfiles/transmission-1.11/libtransmission’
make: *** [all-recursive] Error 1

I've searched everywhere and can't fig out what's wrong. I had 1.03 installed and working but want a newer version because with 1.03 I don't see the details button next to resume all button. I did a make uninstall for 1.03. Reinstalled openSSL and Pkg-Package. What is causing these errors and how can i fix it?

Update: I've gotten 1.06 installed. Why do I get that error when I try to install 1.10 or 1.11?

Finally got my box today.

I have both transmission and clutch up and running thanks to optware and the guide at http://www.mybook-linux.co.nr/transmission.html.

However, the physical power off button does not appear to be functioning on my device anymore.

The only programs I have installed are transmission and clutch along with the required programs/libs to run it.

the only modification to the start script is to enable SSH which worked fine and

The following in my post_network_start.sh script

 start() { if [ ! -e "$POST_NETWORK_STARTED_FILE" ] then $SCRIPTS_PATH/crond.sh start # $SCRIPTS_PATH/mionet.sh start $SCRIPTS_PATH/transmission.sh start touch $POST_NETWORK_STARTED_FILE fi } stop() { if [ -e "$POST_NETWORK_STARTED_FILE" ] then $SCRIPTS_PATH/transmission.sh stop # $SCRIPTS_PATH/mionet.sh stop $SCRIPTS_PATH/crond.sh stop rm $POST_NETWORK_STARTED_FILE fi } 

and the following in my transmission.sh file

 PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/bin NAME="Transmission" DESC="Torrent Daemon" case "$1" in start) echo -n "Starting $DESC: " transmission-daemon -s /tmp/transmission-socket echo "$NAME." sleep 2 chmod -R 777 /tmp/transmission-socket chown -R www-data:www-data /tmp/transmission-socket sleep 2 transmission-remote -f /shares/internal/PUBLIC/bittorrent/ ;; stop) echo -n "Stopping $DESC: " killall transmission-daemon echo "$NAME." ;; *) N=/etc/init.d/$NAME echo "Usage: $N {start|stop}" >&2 exit 1 ;; esac exit 0 

Any help would be muchly appreciated

Regards,

Chris

It looks like I got two files with different lists of torrents and at start it loads an old one and when I manually start it loads the right one.
I can even do changes (delete/pause a torrent) in the old one and they are there the next time that list of torrents come up.
It's pretty annoying to always have to manually restart it if I have to reboot my mybook or something.

Someone knows what to do about it?

execve failed for: /usr/local/bin/php-cgi No such file or directory

Have you installed php-fcgi package in optware?

If yes, you need to tell lighttpd where to look for the executable. It is currently looking here /usr/local/bin/php-cgi. Obviously it would actually be stored somewhere in /opt.
Edit lighttpd.conf to specify the location of your php-fcgi binary.

e.g.

 # Bruce - Removed host & port and replaced with a socket # "host" => "127.0.0.1", # "port" => 1026, fastcgi.server = ( ".pl" => (( "socket" => "/tmp/lighttpd.fcgi.socket", "bin-path" => "/usr/www/lib/nasMaster.pl", "check-local" => "disable", "min-procs" => 1, "max-procs" => 1, "idle-timeout" => 30, "bin-environment" => ( # Environment variables for nasMaster.pl "PERL5LIB" => "/usr/www/lib", "NAS_NBIN" => "/usr/www/nbin", ), )), "nasMaster.pl" => (( "socket" => "/tmp/lighttpd.fcgi.socket", "check-local" => "disable", )), ".php" => (( "bin-path" => "/opt/bin/php-fcgi", "socket" => "/tmp/php.socket", )) ) 

2008-03-06 06:15:16: (mod_fastcgi.c.892) execve failed for: /usr/local/bin/php-cgi No such file or directory
2008-03-06 06:15:16: (mod_fastcgi.c.920) child exited: 2
2008-03-06 06:15:16: (mod_fastcgi.c.923) if you try do run PHP as FastCGI backend make sure you use the FastCGI enabled version.
You can find out if it is the right one by executing 'php -v' and it should display '(cgi-fcgi)' in the output, NOT (cgi) NOR (cli)
For more information check http://www.lighttpd.net/documentation/fastcgi.html#preparing-php-as-a-fastcgi-program
2008-03-06 06:15:16: (mod_fastcgi.c.1200) [ERROR]: spawning fcgi failed.
2008-03-06 06:15:16: (server.c.673) Configuration of plugins failed. Going down.

php -v
PHP 5.2.5 (cli) (built: Jan 18 2008 08:45:40)
Copyright (c) 1997-2007 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies

i use optware for installing

how can i fix this

Say I only want a max of 3 downloads at the same time, How would I need to do that?

Anyway- I hardly think that a clutch package is needed. All you need to do is drop a single directory into your web-root. Not worth the hassle of trying to replace the default lighttpd.

I know all can be done using ssh. But I prefer fontends. That's the whole reason behind using transmission instead of rtorrent.

I don't see how a website could use up ram? It's nothing more then a set of .pl scripts which can create/remove/modify samba users/shares/settings. I have everything copied over but I still got some '403 -forbidden' errors.

I have to search where to disable the default lighthttpd daemon and replace it with the other one installed with optware. And then compare those configuration files to fix permission problems.

These are the configuration steps after the installation with optware which differ from the howto from koolas. We start at section 4.3.1. Socket Settings:

We can skip the modifications at the remote/data/socket.txt as it already contains a link to the socket file.

Start the transmission daemon (note the dash instead of the point):

 # transmission-daemon -s /tmp/transmission-socket 

Create the communication socket (note the dash instead of the point):

 # cd /root/.transmission/daemon # ln -s /tmp/transmission-socket socket 

From here follow the steps at koolas howto.
You are now able to indeed able to connect to clutch at http://mybookworldIP:8081/clutch (notice the lower case 'c')

That's all… please notice that you have 2 lighthttpd servers running which *could* cause some trouble. I'm looking for a way to get the default webgui working on the optware version of lighthttpd server.

I mainly did it this way because I didn't know the gumstix feed had a clutch package

I just installed clutch via Optware and it also installed lighttpd as dependancy.
Seems to work perfectly well when visiting http://mybookworldIP:8081/clutch/, however it seems to break the in built lighttpd installation. I think I'll revert back to my previous method.

The (good looking) guide provided by koola is nice but it covers the whole installation procedure as a source installation. It's hard to determine what steps I should do to get transmission/clutch working with the optware installation.

I installed both transmission and clutch with ipkg. Transmission seems to be running. But I don't see Clutch anywhere in /usr/www/lib so I figure it is impossible to reach it.

 # ps auxww | grep transmission root 5548 0.0 2.5 2576 776 ? S 19:18 0:00 transmission-daemon root 5549 0.0 2.5 2576 776 ? S 19:18 0:00 transmission-daemon root 5550 0.0 2.5 2576 776 ? S 19:18 0:00 transmission-daemon root 5783 0.0 1.0 660 328 pts/2 S+ 19:39 0:00 grep transmission 

As Clutch is a web frontend for transmission-remote I assume there is no process running.

Perhaps someone got some pointers on what to do after the installation to get it working?

Cheers,
San

Another reason to use the Optware feed, considering it is keeping pretty up to date.

On another note, the Clutch tarball comes with /tmp/transmission-socket as the default location for the socket file (as opposed to /tmp/transmission.socket). I think the guide should mirror this, otherwise every time people update they will have to remember to manually change the path (while not hard, can be annoying).

I get an assertion failure, see http://forum.transmissionbt.com/viewtopic.php?t=3978

Transmission guide also updated!

Unfortunately it requires a modified version of transmissioncli, this is a problem for me because I already have a perfectly working Transmission+Clutch setup via Optware. So basically I am going to leave tf idle until I can be bothered breaking my current setup.

Anyone else would care to try I would love to hear the results. tf-b4rt can use some other clients but I don't think any are as light at transmission.

From looking at this guide, it could get this rss feed for example and download the file.

I was wondering by the way:
Does anybody now of some sort of RSS-deamon?
It could watch RSS-feeds for torrents with certain keywords and then put it in a watch-dir (see the watch-dir topic for the watch-dir script).

Then one could have the utorrent-like RSS-functionality! :)

(Or am I just mumbling?)

It fixes a load of bugs in 2.0, Transmission guide has been updated.

mybook-linux transmission guide

Not experienced any errors in the new build yet, guess I'm lucky.

 transmission-daemon transmission-proxy transmission-remote transmissioncli 

Looks like the missed a - on the cli one.

But I have always run from SVN so I'm not sure if it is a regression since 0.1.

Oh and you can use transmission-remote -r <hash> to remove the torrent.

Or is it my build that screwed around?

If you still have the install folder, run

 make uninstall 

Then build and install Transmission 1.00, or just make it and install over the top of the previous.

It's all working though and that error in the .h file is gone now.

Will update the guide shortly when time allows :)

I changed the path clutch/remote/data/sockets was pointing to, to the socket file in /root/.transmission/daemon/socket

After that it all worked again, torrents are being checked and all that :D

Yes, I'm having a similar problem. The first time I got transmission/clutch running I managed to download a torrent pretty quickly. Now, however, whenever I try to upload a torrent nothing happens. I've checked permissions in the folders and they are all the same.

I've also noticed the CPU runs near 100% on the transmission-daemon. I don't think I'm having the harddrive problem though…

I've also noticed that I can't kill the transmission-daemon processes and I'm forced to reboot.

I just find it odd that it all worked great the very first time but now it's unusable. It doesn't pick up torrents in the /shares…/torrent directory and it can't upload.

Argh! I've spent 4 days trying to get this to run and I am so close now!!

Can anyone help Muki and me?

You are a star! It's working!!

Many, many thanks.

I