Transmission 3 0

Papka__ Posts: 5 Joined: Fri Oct 24, 2008 6:20 am settings.json Is it possible to get complete list of setts for transmission? I check settings.json, but seems it's not full list. For example on the forum I found that it's possible to add setts for proxy server. volenin Posts: 16 Joined: Sat Feb 07, 2009 5:44 pm Re: settings.json Post by volenin » Sat Feb 07, 2009 6:21 pm Yeap, I vote for this one too. The next best thing to the complete settings file I got to was to run transmission from the desktop, which generated settings.json file with much more settings that are covered on the trac. Running transmission in headless mode is very hard because quite important settings are not being covered in the documentation right now... gdb Posts: 1 Joined: Fri May 01, 2009 12:47 pm Re: settings.json Post by gdb » Fri May 01, 2009 1:24 pm Hi Im running transmission-daemon on Ubuntu server 8.10I have created a file $HOME/.config/transmission-daemon/settings.json with my required settings( "download-dir": "\/media\/store\/incoming", ) but for some reason the file is not read all the permissions are correct and the *.restore files are read.when I check the Preferences on the web gui it shows the download dir is /Does anybody know why transmission-daemon is not reading the settings.json filecat /home/transmission/.config/transmission-daemon/settings.json{ "blocklist-enabled": 0, "download-dir": "\/media\/store\/incoming", "download-limit": 100, "download-limit-enabled": 0, "encryption": 2, "max-peers-global": 200, "peer-port": 51413, "pex-enabled": 1, "port-forwarding-enabled": 0, "rpc-access-control-list": "+127.0.0.1", "rpc-authentication-required": 0, "rpc-password": "", "rpc-port": 9091, "rpc-username": "3", "upload-limit": 3, "upload-limit-enabled": 1, "proxy": 192.168.0.106, "proxy-port": 3128, "proxy-enabled": 1} volenin Posts: 16 Joined: Sat Feb 07, 2009 5:44 pm Re: settings.json Post by volenin » Sun May 03, 2009 4:48 pm Have the same problem after upgrading to SVN 8322 (either 1.6beta1 or couple of updates later). settings.json file for daemon is not longer being read. Has the default TRANSMISSION_HOME directory changed? I'm not redefining it right now in the init.d script, so it (supposedly) defaults to $HOME/.config/transmission-daemon/ directory....EDIT: correction: the settings.json file seems to be read after all, it's just not all (I'd rather say - just a few) settings are being

Output counters: 1 bytes per output counter (inputs 1 to 8). Type 2: 4 bytes for the date and time, 2 bytes LSB for frequency value (base 0.1Hz), 2 bytes LSB for input counter, 1 byte (optional) for battery percentage. Type 1: 4 bytes for the date and time, 2 bytes LSB for frequency value (base 0.1Hz), 1 byte (optional) for battery percentage. Type 2: 30 byte for 5 measures (6 byte for every measure, 4 bytes date and time as defined in Note 1, 2 bytes LSB for counter value) and 1 byte (optional) for battery percentage. Type 1: 2 bytes LSB per input counter (inputs 1 to 16).Only present in MCF-LWWS01 and MCF-LW06DAVKPįor input counters message refer to Note 9įor frequency meter message refer to Note 10įor output counters message refer to Note 11 Any other value meanings that the Vantage does not have the 3 hours of bar data needed to determine the bar trend. It is one of these values: -60 = Falling Rapidly = 196 (as an unsigned byte), -20 = Falling Slowly = 236 (as an unsigned byte), 0 = Steady, 20 = Rising Slowly, 60 = Rising Rapidly, 80 = ASCII “P” = no trend info is available. Signed byte that indicates the current 3-hour barometer trend. Single Bit meaning is: 0x01 = Rain, 0x02 = Cloud, 0x04 = Partly cloudy, 0x08 = Sun, 0x10 = Snow. The value is a signed two byte value in whole degrees F. Weather station date and time (as for Note 1) (0° is no wind data, 90° is East, 180° is South, 270° is West and 360° is north)Progressive frame index, increased at each transmission with the same identifier In case of EGK-LW20L00 and EGK-LW20W00, with accelerometer enabled, the inputs 0 represents the accelerometer status (Input = 1 start of accererometer event start, input = 0 end of accelerometer event).įor MCF-LW06KAM, “Y” is the sequential number of the transmission in progress, is incremented at the end of each transmission.įor MCF-LW06485, successful reading, “Y” is the sequential number of the transmission in progress, is incremented at the end of each transmission, refer to Note 2įor MCF-LW06485, error reading, “Y” is the sequential number of the transmission in progress, is incremented at the end of each transmission, refer to Note 2įor MCF-LWWS00, MCF-LWWS01, MCF-LW06DAVK and MCF-LW06DAVKP, “Y” is the sequential number of the transmission in progress, is incremented

61 1 Secondary index of db.rev db.revdx 54 10 Revision records for revisions deleted at the head revision db.revfs 65 1 Client filesystem file sizes db.revhx 55 10 Revision records for revisions NOT deleted at the head revision db.review 35 1 User's review mappings db.revpx 56 10 Pending revision records db.revsh 58 10 Revision records for shelved files db.revstg 64 10 Temporary revision records for storage upgrade process db.revsx 57 10 Revision records for spec depot files db.revtr 76 10 Rev table for huge traits db.revtx 63 10 Task stream revision records db.revux 60 10 Revision records for unload depot files db.rmtview 13 1 View data for remote specifications db.scanctl 49 0 ScanCtl db.scandir 48 0 Scandir db.sendq 111 6 Parallel file transmission work queue db.sendq.pt 112 6 Per Client transmission work queue db.server 10 3 Server specifications db.stash 14 1 Stash data db.storage 51 2 Track references to archive files db.storageg 52 1 Track references to Graph Depot archive files (for future use) db.storagesh 50 2 Track references to shelved archive files db.storagesx 53 0 Digest and filesize based index for db.storagesh, for finding shelved files with identical content db.stream 22 3 Stream specifications db.streamq 26 0 Track streams for which the stream views should be regenerated db.streamrelation 23 0 Relationships between streams db.streamview 24 2 Precomputed stream views db.streamviewx 25 2 Indexing for precomputed stream views db.submodule 89 0 Submodule configuration data db.svrview 11 0 View data for servers specifications db.template 29 3 Streams templates db.templatesx 30 3

Conditions is your normal operating load. How much your suspension compresses and extends defines the working driveline angle range. This can be extremely important to keep in mind if the vehicle is airbagged. We will take a look at this further into the article (see Step *5).1.) The first step to setting the proper driveline angle is to as align the transmission tailhousing with the pinion. When looking down the tail of the transmission at the pinion yoke, you want the tail to be as vertically and horizontally centered with the pinion yoke as possible. Most of the time, adjusting the transmission is not possible, it simply is where it is. The transmission tailhousing being vertically, horizontally, or both, out of centered alignment with the pinion yoke is often just a reality, and is typically not an issue for 15 degrees or less of misalignment, which is almost always the case for street rods. So you are likely ready to move on to Step 2. However, if you are rebuilding your rod, swapping in a new motor and/or transmission, or making modifications to the transmission crossmember, be sure to align the transmission tailhousing with the pinion. Here is a picture of how a properly centered drive shaft should appear, looking from the rear pinion towards the transmission tailhousing (click on thumbnails for larger image).Notice in the picture the transmission tailhousing / slip yoke sits at ~ -3 degrees:2.) Now use an angle finder to measure the angle of the driveshaft. Notice in the picture the driveshaft sits at 0 degrees.3.) Now use an angle finder to measure the angle of the pinion yoke. The best way to measure this to turn the yoke until one of the flat yoke facets faces the ground, and then place the angle finder on

Re: Asset UPNP not showing upOk tried it with no change. I now do notice that after starting an app it finds 2 UPNP servers immediately and Asset is sometimes found after a few minutes but most if the times it does not show up. Can this be related to virtual machines running on the same server (Asset is not installed on virtual machine but on the host). Network config:Name: EthernetDescription: Intel(R) Ethernet Connection (2) I219-VPhysical address (MAC): Status: OperationalMaximum transmission unit: 1500Link speed (Receive/Transmit): 1000/1000 (Mbps)DHCP enabled: NoIPv4 address: 192.168.10.10/24IPv6 address: Default gateway: 192.168.10.1DNS servers: 192.168.10.1DNS domain name: DNS connection suffix: DNS search suffix list: Network name: Network 2Network category: PrivateConnectivity (IPv4/IPv6): Connected to Internet / Connected to unknown network Name: vEthernet (TTorrie)Description: Hyper-V Virtual Ethernet AdapterPhysical address (MAC): Status: OperationalMaximum transmission unit: 1500Link speed (Receive/Transmit): 1000/1000 (Mbps)DHCP enabled: YesDHCP servers: 192.168.10.1DHCP lease obtained: &*8206;donderdag &*8206;21 &*8206;juni &*8206;2018 12:23:16DHCP lease expires: &*8206;vrijdag &*8206;22 &*8206;juni &*8206;2018 12:23:16IPv4 address: 192.168.10.29/24IPv6 address: fe80::f05b:91c1:be2:c51%6/64Default gateway: 192.168.10.1DNS servers: 213.46.228.196, 62.179.104.196DNS domain name: DNS connection suffix: DNS search suffix list: Network name: Network 2Network category: PrivateConnectivity (IPv4/IPv6): Connected to Internet / Connected to unknown network Name: vEthernet (Default Switch)Description: Hyper-V Virtual Ethernet Adapter *2Physical address (MAC): Status: OperationalMaximum transmission unit: 1500IPv4 address: 172.30.95.193/28IPv6 address: fe80::b4f0:5d89:18b0:6ef2%9/64DNS servers: fec0:0:0:ffff::1%1, fec0:0:0:ffff::2%1, fec0:0:0:ffff::3%1Connectivity (IPv4/IPv6): Connected to unknown network, no traffic

Maki.ato Posts: 70 Joined: Fri Apr 15, 2011 10:20 pm Transmission re-downloads stuff already completed? This is a weird one.Whenever I start transmission (either manually, or forced by a power out) transmission picks between 1 to 3 torrents that already completed and were seeding and downloads them from scratch. It shows their completing is at 0%. If I stop those downloads and verify them they go back to 100% and I can continue seeding as normal.This started happening with v2.83. It also happens with 2.84.HELP!Technical details: I'm running transmission 2.84 on a D-Link DNS-323. maki.ato Posts: 70 Joined: Fri Apr 15, 2011 10:20 pm Re: Transmission re-downloads stuff already completed? Post by maki.ato » Tue Aug 05, 2014 9:02 am I guess my first post was "a bit" lacking in detail, so here goes: If it's unclear, I'm running Tranmsission Daemon on the DNS-323.Uptime is 11 days (since the last power out, that's when I noticed this issue).Transmission, its config file, log file, resume files, torrents, libs, compete/incomplete data all reside on the same partition on the same physical drive. The setup is simple, no RAID, JBOD or anything of the sort.The drive is spun up, the partition is mounted.I stopped tranmission, up-ed the message level to 3 (debug log level, previously it was 1) and restarted it. Sure enough, one complete torrent was at 0% and downloading. I immediately stopped it and verified it. Yep, 100% complete.Here's all the log lines relevant to it:Code: Select all...[2014-08-04 19:40:06.408 IDT] Couldn't save file "/var/lib/transmission/resume/Some Torrent.55023b328987ef73.resume": No such file or directory (variant.c:1219)[2014-08-04 19:40:07.410 IDT] Some Torrent Unable to save resume file: No such file or directory (torrent.c:536)[2014-08-04 19:40:07.411 IDT] Couldn't save file "/var/lib/transmission/resume/Some Torrent.55023b328987ef73.resume": No such file or directory (variant.c:1219)[2014-08-04 19:40:07.412 IDT] Some Torrent Unable to save resume file: No such file or directory (torrent.c:536)...[2014-08-05 11:46:13.916 IDT] Couldn't read "/var/lib/transmission/resume/Some Torrent.55023b328987ef73.resume": Input/output error (utils.c:233)[2014-08-05 11:46:13.917 IDT] Some Torrent Couldn't read "/var/lib/transmission/resume/Some Torrent.55023b328987ef73.resume" (resume.c:715)...[2014-08-05 11:46:33.420 IDT] Some Torrent Announcing to tracker (announcer.c:1552)...[2014-08-05 11:46:33.442 IDT] Some Torrent Got 9 peers from tracker (torrent.c:564)...[2014-08-05 11:46:42.458 IDT] Some Torrent Scrape successful. Rescraping in 1800 seconds. (announcer.c:1372)...[2014-08-05 11:46:59.443 IDT] Some Torrent [LAZY] checking just-completed piece 822 (torrent.c:3250)[2014-08-05 11:47:01.539 IDT] Some Torrent Pausing (torrent.c:1857)[2014-08-05 11:47:01.540 IDT] Saved "/var/lib/transmission/resume/Some Torrent.55023b328987ef73.resume" (variant.c:1214)...[2014-08-05 11:47:01.541 IDT] Some Torrent Announcing to tracker (announcer.c:1552)... maki.ato Posts: 70 Joined: Fri Apr 15, 2011 10:20 pm Re: Transmission re-downloads stuff already completed? Post by maki.ato » Tue Aug 05, 2014 9:38 am More details:It's probably not a HDD failure. I ran a SMART quick scan on the drive and all's well. "Completed without error".In the previous log it seems that the issue has something to do with saving the resume file. That part of the log is from when the message level was set to 1. Now that it's 3, it's time to stop/start again and see what happens.After stopping, I don't see in the log any new resume file saving, and when I start transmission daemon again all's good.I do, however, see a lot of