Transmission

Err, how do I make a wiki page?

The instructions say that I should start by linking to it from an existing page. I was going to link it under More Documentation on WikiStart, but I can't figure out how to edit WikiStart to make the link.

Sure, I can do that. I'll post a link after I finish it up.

Oh, and FWIW, when I ran the finked version of the daemon with no arguments, it looked to ~/.config/transmission-daemon/ for its config files, so no trouble there either.

Well, that was simple enough. Eliminating the KeepAlive key seems to have tamed the daemon.

Now we'll just hope that the daemon is stable/tenacious enough to keep itself alive. /me knocks wood.

woot

I installed 2.13 via fink and now watch-dir is working as it should. It even trashes the .torrent files after adding them. When I installed it, I noticed that fink included libevent , which I'm guessing is needed to make the watch-dir thing actually realize something has changed.

Now I just ...

Good guess, but no. Downloads go to /Users/surfer/Downloads/Torrents/ which is the same configuration I used in the .app.

The Fink version just got updated to 2.13, so maybe I'll give that a try and see if it helps. Perhaps I managed to mess up the build (though it seemed like a pretty ...

TheChipmunks:~ surfer$ defaults read org.m0k.transmission
{
AutoImport = 1;
AutoImportDirectory = "/Users/surfer/Downloads";
[snip]
Looks like it's set up correctly in defaults as well as the JSON.

And as I said, when I launch the daemon, it explicitly tells me it's monitoring /Users/surfer ...

Thanks for the reply.

Doesn't OS X use /Users/surfer/Library/Application Support/Transmission or [transmission-daemon] and also use a plist for settings (~/Library/Preferences/org.m0k.transmission.plist)?
I'm not sure about the locations you mentioned, but I think I got the one I'm using from the ...

Okay, I'm trying to transition from using Transmission.app on my MacBook to using transmission-daemon on my iMac, using the 'Book to puppet the daemon, and I'm having some issues. Sorry if most/all of this has been covered before, but I wasn't having much luck searching the forums.

First, when I ...

PEBCAK

Seems I was setting script-torrent-done in the JSOM instead of script-torrent-done-filename. ><

Well, I got 2.13 installed.

I'm able to get it to run my post-processing script, but like anville, I do need to resort to transmission-remote to tell it where to find the script, so while the functionality is definitely there, for whatever reason, it's not reading the script location from the JSON ...

Well, I seem have gotten transmission-daemon to behave by disabling PEX.

Then I was having trouble getting it to respect the trash-torrent and torrent-done flags—it does seem to be reading the JSOM file, for what it's worth—so I decided to try using transmission-remote to get it to do the post ...

No spaces or other oddness in $TR_TORRENT_DIR. I don't have any examples still laying around, but I'm reasonably sure $TR_TORRENT_NAME is clean as well. (I didn't need to treat them specially in the shell when I massaged them manually, etc.) Good guess, but I don't think it's the issue.

I'll try ...

Okay, thanks. I just got mediatomb launchd 'd on the iMac and I was going to start working on transmission-daemon tonight, so I guess I'll report back and let you guys know how it goes.

Speaking of the torrent-done script though, anyone have any idea why sometimes it seems to not fire? My script ...

x190, so are you saying that the script will execute as long as it's set up properly in the JSON file? I'm considering moving from the GUI client to the daemon, but running the torrent-done script is pretty important to my flow.

Can anyone confirm/deny this before I go through the trouble of ...