If you need some more customisation and automatic handling than Download Station can provide, JDownloader is your choice. The program is well known on the regular PC and can be used – thanks to Java – on almost all contributing systems.
The prerequisite is of course Java on DSM – this can be installed over the Package Center and should be updated immediately. An update is quite simple – after the installation in the Package Center open Java. The latest Java version is available for download from Oracle.
Also, the JDownloader app can of course not installed via the Package Center. Here, third-party sources are needed, for example, https://spk.netzbaer.de. To be able to install you must first allow other sources in the settings for the Package Center.
The installed package is a headless JDownoader. To access JDownloader you need an account at my.jdownloader. This information (login and password) is requested during the installation of JDownloader on DSM.
Last but not least – if you are planning a lot of downloads, it happens quite quickly that the DSM system partition is at 100% usage. The result is that login to DSM is not possible and – in the worst case – even one of the basic DSM configurations is damaged. This means that for next reboot not DSM interface but migration assistant would appear.
Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 1998672 1982288 0 100% / none 507380 0 507380 0% /dev /tmp 511816 1036 510780 1% /tmp /run 511816 1568 510248 1% /run
A real solution does not exist – either you delete the log data manually manually, or you send them directly into the “nothing”:
rm /var/log/JDownloader.log ln -sf /dev/null /var/log/JDownloader.log
With these commands, the current JDownloader log data is deleted and all further log data will be written to /dev/null (means to nowhere). It is recommended to check after update of JDownloader if /var/log/JDownloader.log is still a symlink to /dev/null – in case of doubt, simply run the above commands again.