Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
*Yet another Torrent thread
After trying some torrent client solutions (D-Link fw 1.05 buildin, MLdonkey) i found no client which satisfied me.
D-Link client seems not sophisticated. It disappeared on my DNS after few weeks.. IMO the 'official' client is not on main focus at D-Link. Its just meant to be a 'goody'.
MLDonkey comes with a huge variety of features but seems to be overloaded for useage with the DNS. It takes lots of memory.
So I tried btpd included in ffp 0.5. This works like a charm. Slim and fast and very resource friendly. Mem usage at around 4 %.
The only problem I have now the client seems to stop without any reason. I log in again after while to see my downloads and it couldnt connect to the deamon. 'btcli: cannot open connection to btpd in /home/root/.btpd: Connection refused'
Downloads are not finished at this time. After restarting the client, torrent downloads continue.
http://www.murmeldjur.se/btpd/README
Any others haveing this issue? Maybe its caused by HD sleep mode?
Last edited by mcmurphy (2008-09-11 17:20:00)
Offline
mcmurphy wrote:
'btcli: cannot open connection to btpd in /home/root/.btpd: Connection refused'
/home/root is on the ramdisk with only about 2MB free space. The README says "btdp will store information and write its log in $HOME/.btpd." Are you sure it's not running out of disk space? Try using the -d switch.
Also, you should consider running btpd as an ordinary or even special user. Running bittorrent clients as 'root' looks dangerous.
Offline
I try to start / run as different user.
Last edited by mcmurphy (2008-09-11 17:33:37)
Offline
What about mounting a folder on the HD to /home/root/.btpd? This could be done in the startup script and would then write to the HD instead of ramdisk.
Something like: mount -t ext2 /mnt/HD_a2/.btpd /home/root/.btpd
Of course you would have to first create the /mnt/HD_a2/.btpd directory.
Last edited by bq041 (2008-09-11 17:41:02)
Offline
fonz wrote:
PS: Any messages in the log file?
its not mentioned in the ffp.log
Offline
bq041 wrote:
What about mounting a folder on the HD to /home/root/.btpd? This could be done in the startup script and would then write to the HD instead of ramdisk.
Something like: mount -t ext2 /mnt/HD_a2/.btpd /home/root/.btpd
Of course you would have to first create the /mnt/HD_a2/.btpd directory.
I will try this later. Thanks. But as fonz mentioned security issues on running as root, I probably will try some user.
Offline
bq041 wrote:
Something like: mount -t ext2 /mnt/HD_a2/.btpd /home/root/.btpd
That would be "mount --bind ....", right?
Anyway, -d or a different user with $HOME on disk should take care of it.
Offline
btpd: content.c: 272: cm_put_bytes: Assertion `!has_bit(bf, begin / (1 << 14))'
failed.
this was last message of tonite. I dont remember to have stopped the client.
Offline
fonz wrote:
That would be "mount --bind ....", right?
Anyway, -d or a different user with $HOME on disk should take care of it.
From a traditional standpoint, yes, but in the version of busybox you compiled in ffp 0.5, it is not needed. The regular mount command without the bind option works. To keep in sync with the documentation, though, the bind or rbind option should probably be included.
Offline
bq041 wrote:
From a traditional standpoint, yes, but in the version of busybox you compiled in ffp 0.5, it is not needed.
Didn't know that. The busybox people do funny things, sometimes.
Offline
Here is the solution:
A regular start of the btpd deamon makes it executing in root directory which is traditionally not the best in DNS323.
After having a look in here http://www.murmeldjur.se/btpd/README and with little guidance by fonz, I just started the daemon in another directory.
btpd -d /mnt/HD_a2/newpathtobtpd/
When using the btlcli command you have to give the path where btpd is running also.
btcli -d /mnt/HD_a2/newpathtobtpd/ add -d torrentdirectory (to be created) torrentfile.torrent
Offline
Still an error after a while..
btpd: download.c: 49: dl_on_download: Assertion `!peer_wanted(p) || peer_laden(p)' failed.
Offline