slint and transmission-cli questions

Fri May 4 14:43:51 UTC 2018

This is Jude Dashiell, this time transmission-cli ran without those two 
errors.  I'm not sure but will check the downloads shortly but it could 
be clearing these errors may have finally allowed me to get an accurate 
download.

On Fri, 4 May 2018, Didier Spaier wrote:

> Date: Fri, 4 May 2018 03:00:22
> From: Didier Spaier <didier at slint.fr>
> To: blinux-list at redhat.com
> Cc: B Watson <yalhcru at gmail.com>, Jude DaShiell <jdashiel at panix.com>
> Subject: Re: slint and transmission-cli questions
> 
> Hello Jude,
>
> I quote below the main part of the answer I received from B Watson.
> He is not registered to this list so please CC him in your further
> posts on this topic.
>
>> Argh. You didn't include the actual error messages in the mail you sent me
>
>> Also, /etc/sysctl.conf has nothing to do with systemd. It's for setting
>> kernel tunables. It's basically a frontend or replacement for commands
>> like "echo 1 > /proc/sys/whatever", and it exists & works fine on
>> Slackware.
>
> I confirm that for Slint as well, and we do have the sysctl command
> that can handle this file, as noted in "man sysctl"
>
> So to avoid these errors or warnings:
>> [2018-05-03 14:39:36.371] UDP: Failed to set receive buffer: requested 4194304, got 425984
>> [2018-05-03 14:39:36.371] UDP: Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf
>> [2018-05-03 14:39:36.371] UDP: Failed to set send buffer: requested 1048576, got 425984
>> [2018-05-03 14:39:36.371] UDP: Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf
> I wrote this as root:
> echo "net.core.rmem_max = 4194304 >> /etc/sysctl.conf
> echo "net.core.wmem_max = 1048576" >> /etc/sysctl.conf
> sysctl -p
>
> The latter command's output is, as expected:
> net.core.wmem_max = 1048576
> net.core.rmem_max = 4194304
>
> Then this command:
> transmission-cli -w /tmp http://www.slackware.com/torrents/slackware64-14.2-install-dvd.torrent
> ran without errors.
>
> Let us know if that works for you as well.
>
> Greetings,
>
> Didier Spaier
>
>
> Le 03/05/2018 ? 14:50, Linux for blind general discussion a ?crit?:
>> Hello Anonymous;)
>>
>> I just built and installed transmission, using the SlackBuild from here:
>> https://slackbuilds.org/repository/14.2/network/transmission/
>> I ran the script directly but could as well have run as root:
>> spi -i transmisson
>> (to get the package built and installed. By default all parts are built, this includes beyond the cli: GTK, Qt and the daemon.)
>>
>> Then I issued this command:
>> transmission-cli -w /tmp http://www.slackware.com/torrents/slackware
>> I get the same errors, however it works
>>
>> didier[~]$ transmission-cli -w /tmp http://www.slackware.com/torrents/slackware64-14.2-install-dvd.torrent
>> transmission-cli 2.93 (3c5870d4f5)
>> [2018-05-03 14:39:36.370] Transmission 2.93 (3c5870d4f5) started
>> [2018-05-03 14:39:36.371] RPC Server: Adding address to whitelist: 127.0.0.1
>> [2018-05-03 14:39:36.371] UDP: Failed to set receive buffer: requested 4194304, got 425984
>> [2018-05-03 14:39:36.371] UDP: Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf
>> [2018-05-03 14:39:36.371] UDP: Failed to set send buffer: requested 1048576, got 425984
>> [2018-05-03 14:39:36.371] UDP: Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf
>> [2018-05-03 14:39:36.371] DHT: Reusing old id
>> [2018-05-03 14:39:36.372] DHT: Bootstrapping from 44 IPv4 nodes
>> [2018-05-03 14:39:36.704] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
>> [2018-05-03 14:39:36.704] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
>> [2018-05-03 14:39:37.442] Saved "/home/didier/.config/transmission/torrents/slackware64-14.2-iso.85922fbee6dce5e2.torrent"
>> [2018-05-03 14:39:38.733] Port Forwarding (UPnP): Found Internet Gateway Device "http://192.168.0.254:5678/control/wan_ip_connection"
>> [2018-05-03 14:39:38.733] Port Forwarding (UPnP): Local Address is "192.168.0.10"
>> [2018-05-03 14:39:38.756] Port Forwarding (UPnP): Port forwarding through "http://192.168.0.254:5678/control/wan_ip_connection", service "urn:schemas-upnp-org:service:WANIPConnection:1". (local address: 192.168.0.10:51413)
>> [2018-05-03 14:39:38.756] Port Forwarding (UPnP): Port forwarding successful!
>> [2018-05-03 14:39:38.756] Port Forwarding: State changed from "Not forwarded" to "Forwarded"
>> Progress: 16.7%, dl from 39 of 50 peers[2018-05-03 14:39:56.000] slackware64-14.2-iso: Starting IPv4 DHT announce (poor, 16 nodes)
>> Progress: 19.8%, dl from 49 of 50 peers (2.08 MB/s), ul to 0 (0 kB/s) [0.00]
>>
>> So I don't think you should worry about the errors.
>>
>> I never used transmission before so can't answer your other question, but I am CCing B. Watson, the transmission SlackBuid maintainer, who certainly knows more.
>>
>> Le 03/05/2018 ? 13:44, Linux for blind general discussion a ?crit?:
>>> Anyone running transmission-cli on slint?? I get a couple errors when it starts up I think I can turn off by disabling port mapping with the -M option.? Apparently transmission-cli expects to be on systemd machines because both error messages want /etc/sysctl.conf to be updated and have lines added to it.? I don't know what to do for system v systems.? Also, I don't know what port mapping would get me if it were enabled as well as disabled.? Transmission-cli runs after these errors though.
>>>
>>>
>>>
>>> --
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>

-- 