Transmission

HI,

I have 2.13 transmission on asus router (oleg firmware on 32 MB RAM router)
For some reason my daemon processes stopped at some point, or I may chose to stop it.
When restarting the transmission daemon I expect that it reloads my pending torrents and also seeds.
For some time now I must reload ...

raiderG
Wrong, you didn't understand what I was saying: you can stop the daemon and then move/delete/edit/copy-something-else-into the file, when the daemon starts after wards it has to check, call it sanity-check.

Well as it seems it usually it does not do that, otherwise every time when ...

when you list them with transmission-remote -l or in web-ui you only see the newly added ones
You ran the daemon with different settings.json, the original one stored all its info in one place, then you changed to another and the daemon only sees the info on the new place.

Now I managed to run ...

I have managed to make it accept adding new torrents (solved the issue with web-ui by setting rpc-enabled=true).
I thing that for most of the time the issue for inactivity was because *somehow* even though I have lots of torrents pending and some other big chunk of them for seeding, when you list ...

SIGINT and SIGTERM stops the daemon cleanly.

But the "doesn't re-check" is not going to happen, it always checks when it starts up. Think about it, anything could have been changed when it was stopped, it has to check.

Actually if you think of the torrent as those many parts that compose a ...

SIGINT and SIGTERM stops the daemon cleanly.

But the "doesn't re-check" is not going to happen, it always checks when it starts up. Think about it, anything could have been changed when it was stopped, it has to check.

Indeed I've seen that stopping with : kill -15 `pidof transmission-daemon ...

So the only problem is the "no activity"?

None at all? You don't see tracker info for instance. Or is it only your torrents not doing anything?

if I do transmission-remote -l to list my torrents nothing. I used to be able to see the web interface with nothing in it. But as I described above now ...

I attach now my settings (doesn't let me to attach anything). This time put the settings to "default" location for daemon to take (the one that appears in logs) daemon starts, some CPU usage at start than drops suddenly to 0:

$ transmission-daemon -f
[22:02:51.213] Transmission 2.13 (11501) started ...

That looks like a mess.

But you are not telling us what are the parameters used with the daemon. The ipkg install doesn't leave a start-up script (or at least it didn't the last time I looked at it, which was very long ago), do you use a script? does it set parameters like which user runs ...

Hi all,

I have an asus wl-500gp, and have been using transmission 2.13 (using oleg firmware, armel ipkg package) quite successfully until recently.
The first symptoms I observed was that while I was editing the json.settings after starting the daemon processes (4 of them ahd all the time, even when ...