Transmission

Excellent work. Looks gorgeous.
What features are currently working?

sigh, oh boy.
You should use the full path to transmission-create. If you don't know where it is, try running the command: Edit: So from your answer I understand that you didn't compile it yourself. Contact the person(s) who compiled it and report this issue.

What's the output from running the command: ldd transmission-create On my NAS it looks like its either statically linked with libevent or more likely that transmission was built without the libevent support: sh-3.2# ldd /ffp/bin/transmission-create ldd: can't open cache '/ffp/etc/ld.so.cache' librt....

You can do it using a command-line tool (i.e. from telnet/ssh) that comes with transmission daemon. sh-3.2# transmission-create --help Usage: transmission-create [options] <file|directory> Options: -h --help Display this help page and exit -p --private Allow this torrent to only be used with the spe...

you need to setup a couple of cron jobs, one to start transmission, the other to shut it down.
read the man pages about cron, crontab, etc.

The receipt assumes some basic linux skills. You should read about adduser. Try "adduser --help" from the command line, and also here: http://linux.die.net/man/8/adduser In addition, you'll probably run into all sorts of permission problems. Lean about it here: http://linux.die.net/Intro-L...

Make sure you're editing the correct settings file. Check how transmission-daemon is started. There's a command-line switch that may be used to override this.
Make sure transmission-daemon is down BEFORE editing settings.json.

What does the log say?
Does the $USER user have the proper permissions for read/write the settings file?
Did you try to: Does that work?

rb07 wrote:Some of the facts don't seem right: if settings.json changed, why you never see the daemon starting with a changed IP? It only changed just after you noticed the loss of RPC... unlikely.

This should be easy to reproduce: Turn off daemon, edit rpc-bind-address in settings.json, start daemon.

rb07 wrote:

maki.ato wrote:There are other accounts of this, or something similar happening?
Can you point me to the thread(s)/Trac Ticket(s)?

No, there are no other reports about this, just about weird thing happening.

Any of them may be related?

There are other accounts of this, or something similar happening?
Can you point me to the thread(s)/Trac Ticket(s)?

We may be looking at two unrelated problems: daemon stops working (very common on NASes, see Wiki ), something changes settings.json (not unheard off, but the reports on this forum never went anywhere). I never entertained the the idea that transmission stopped working. When I think about it, I bel...

I'm experiencing similar excessive memory usage by transmission-daemon on my NAS (and I wrote a watchdog cron job to restart it when it gets out of hand). When started, transmission uses about 60% of available memory, and that number grows to over 100% in a matter of a few days. I seed about ~500 to...

rb07 wrote:I don't think the Mac has anything to do here... he's using a daemon in a NAS, the log is from that NAS (running Linux).

Yup, pretty much so. daemon running on NAS (linux), no syslogd, logging to file using the -e option.

OK, now this gets even stranger. I tried that new grep on the current log (message-level 3) and it produced the (expected) following output: sh-3.2# cd /mnt/HD_a2/.transmission-daemon/ sh-3.2# grep -i rpc transmission-daemon.log [22:12:26.264] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-s...