Hi and Privet Guys from mother Russia. When i have found your distrib i ended to drink vodka and riding a bear and started to testing and tune up this awesome system. It’s really awesome!
Bur i found few bugs, with software installation combinations. Also some of them was fixed by me and i want to share my little expiriencs with your great team and dietpi community.
Transmission memory leak
In sometime transmission started to eat 200-300 and even 500mb of RAM. It’s madness for platforms with 1 or 2gb RAM.
service transmission-daemon stop
Change “cache-size-mb”: 200 to 2.
Transmission WebGUI not reachable after installing ownCloud.
This problem appeared because transmission using it’s own web server. And solution is -
We make proxy settings and transmission daemon will start under it.
I think this option must be implemented in dietpi-launcher in case when we have ownCloud server + Transmission
ownCloud interface not reachable after installation
Interface of not reachable after installation on mentioned at
Access web interface:
url = http://192.168.0.100/owncloud
ownCloud can’t get propper way, if you use ExternalHDD.
After first install i tryed to enter way to my ExternalHDD device: /mnt/cbbfkj-blablabla/ownCloud/
Own cloud swears that way is not correct
chmod 777 -R /mnt/cbbfkj-blablabla/ownCloud/
chmod www-data:www-data /mnt/cbbfkj-blablabla/ownCloud/
Also you must reboot all services after it:
Rtorrent doesn’t get settings file
It’s a great torrent programm but we can’t change prefences while using GUI, after each reboot, all prefences will be canceled to default.
As developers said we must create .rtorrent.rc file in home folder of user. I tried to do this, but after creating of this file rtorrent every time loosing connect from GUI to daemon.
Hope this will help to improve DietPi!