Thanks for the link. Guess it's a known issue.

On Arch Linux, starting deluged throws some warnings which is spamming journalctl. Is there an easy fix to either suppress or fix the underlying problem? % journalctl -u deluged -- Logs begin at Sat 2016-11-26 05:18:07 EST, end at Sat 2016-11-26 05:54:47 EST. -- Nov 26 05:18:12 insomnia systemd[1]: ...

deluge-console

There we go, thanks, Cas.

OK... so you're showing me a package name and its respective dependencies? What I don't understand is which files from the source are required for each package you listed.

THanks for the reply, Cas. As you can see here , a bugreport/feature request was filed 2-3 years ago asking for this split package. Thing is, since there isn't a native compile method to do it, the package maintainer is unsure which files to include in the gtk package and which in the standard packa...

What is your filesystem? Ext4? NTFS? XFS? Did I miss it?

Is there an officially supported way to break up deluge for packaging purposes? I would like to have two packages for Arch Linux: 1) deluge (contains the daemon, deluge-console, and deluge-web) 2) deluge-gtk (contains the deluge-gtk) Here is how the current all-in-one package for Arch linux is creat...

I suppose it isn't any leak. According CPU usage (15%) deluged is doing quite intensive data exchange. It just takes memory for disk cache. For example, my deluged has disk cache 512Mbytes (32768 16k-pages at tab "cache" of settings). So, when my deluged is doing its job (seeding/leeching...

Recently, deluge on my lightweight box has been misbehaving. When running, it (python2?) seems to spawn multiple instances even after halting it from the deluge-console or even from a shell via 'killall deluged'. They just keep running rendering the system is incredible unresponsive when this happen...