NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Transmission 3.00.3 Issues
I'm chasing down two apparent issues, and I also can't seem to find any kind of log file that Transmission is writing to (our old pal /var/log/messages from 4.2 days is gone apparently), so trying to diagnose these behaviors is near impossible. Thus my appeal for help. :)
First, my watchdir -- which I swear was working previously -- has suddenly decided to not work. Automatic is properly placing the torrent files where they should be (I use /data/media/Incomplete/sources) but the files are not recognized by Transmission. The last three lines of my settings.json are
I've verified that the daemon is running with USER set to myuser:mygroup and the file perms of this folder are:
(which I guess is a cruel joke of the ROS'es default file perms... but at least it should work for the daemon, no?
Second, I really miss email notifications from 4.2 days. I borrowed the email script from my 4.2 setup and set the following in settings.json.
The script runs, which is nice. But all the regular Transmission environment variables, such as $TR_TORRENT_NAME are *blank* when the notification is actually sent.
According to ROS, the Transmission add-on is 3.00.3, but Transmission itself (web UI) reports 2.77+... if that matters. :)
First, my watchdir -- which I swear was working previously -- has suddenly decided to not work. Automatic is properly placing the torrent files where they should be (I use /data/media/Incomplete/sources) but the files are not recognized by Transmission. The last three lines of my settings.json are
"watch-dir": "/data/media/Incomplete/sources",
"watch-dir-enabled": true
}
I've verified that the daemon is running with USER set to myuser:mygroup and the file perms of this folder are:
drwxrwsrwx+ 1 guest guest 116 Aug 25 22:52 /data/media/Incomplete/sources/
(which I guess is a cruel joke of the ROS'es default file perms... but at least it should work for the daemon, no?
Second, I really miss email notifications from 4.2 days. I borrowed the email script from my 4.2 setup and set the following in settings.json.
"script-torrent-done-enabled": true,
"script-torrent-done-filename": "/data/Transmission/config/email_alert",
The script runs, which is nice. But all the regular Transmission environment variables, such as $TR_TORRENT_NAME are *blank* when the notification is actually sent.
According to ROS, the Transmission add-on is 3.00.3, but Transmission itself (web UI) reports 2.77+... if that matters. :)
8 Replies
Replies have been turned off for this discussion
- last transmission available for OS 6 is 2.82 :)
- I wil put a 3.00.4 version in community dropbox to force transmission core update
- Well, that's interesting, because the list in your dropbox is:
transmission_2.77-1_amd64.deb
transmission_2.77-1_armel.deb
transmission_2.78.00-1_amd64.deb
transmission_2.78.00-1_armel.deb
transmission_2.80.00-1_amd64.deb
transmission_2.80.00-1_armel.deb
transmission_2.81.00-1_amd64.deb
transmission_2.81.00-1_armel.deb
transmission_2.82-1_amd64.deb
transmission_2.82-1_armel.deb
transmissionr6_3.00.2_all.deb
transmissionr6_3.00.3_all.deb
So we should ignore the "transmissionr6" files? super-poussin wrote: I wil put a 3.00.4 version in community dropbox to force transmission core update
Ah, OK.. thanks :)- done :)
- Installed... Watch dir definitely working now. Need to confirm email script still.
super-poussin wrote: I wil put a 3.00.4 version in community dropbox to force transmission core update
What is the difference between this and installing an app from it's original source? Like$ apt-get install transmission
I really like to know. Is it a compatibility thing or something else?- transmission from apt-get is the core file I compiled and package but it's without frontview GUI
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
