Misc tools¶

The DietPi Survey data file is sent when you install software with dietpi-software and update DietPi with dietpi-update.

The uploaded data is tiny (about 1 KB) and will not affect your internet bandwidth or system performance.

Within the command line program dietpi-survey the exact copy of the transmitted data can be viewed. The transmitted file is written in bash code to allow us faster report page creation (e.g. done for https://dietpi.com/survey).

Following is an example how this file may look like:

#!/bin/bash
((aDIETPI_VERSION[6.34]++))
((aGIT_BRANCH[MichaIng/master]++))
((aDEVICE_NAME[Virtual Machine (x86_64)]++))
((aCPU_ARCH[x86_64]++))
((aCPU_COUNT[2]++))
((aDISTRO_VERSION[buster]++))
((aAUTOSTART_OPTION[${aAUTOSTART_NAME[0]:=0}]++))
((aAUTO_SETUP_AUTOMATED[0]++))
((aNETWORK_INTERFACE[eth0]++))
# -------------------------
# DietPi-Software installs
# -------------------------
((aSOFTWARE[${aSOFTWARE_NAME6_34[103]:=103}]++))
((aSOFTWARE[${aSOFTWARE_NAME6_34[104]:=104}]++))

The tail of the file lists installed software packages by their IDs. The example above shows a very basic system, so only two software packages (#103: DietPi-RAMlog, #104: Dropbear) are installed. To find out the names of the installed software package IDs installed via dietpi-software you can execute

dietpi-software list | grep ' =2'

This gives the IDs, names and info of software. The above example would show

# dietpi-software list | grep ' =2'
id 103 | =2 | dietpi-ramlog: minimal, optimised logging | | https://dietpi.com/docs/software/log_system/#dietpi-ramlog
id 104 | =2 | dropbear: lightweight ssh server | | https://dietpi.com/docs/software/ssh/#dropbear

You can select Opt-in or Opt-out of DietPi Survey by running the following command and follow the instructions:

dietpi-survey

This may also be achieved by setting SURVEY_OPTED_IN=0 (Opt-out) or SURVEY_OPTED_IN=1 (Opt-in) in /boot/dietpi.txt before the first system boot.

To check the actual status, dietpi-survey may be called. The current mode will be pre-selected and highlighted.
Alternatively you can use

grep 'SURVEY_OPTED_IN' /boot/dietpi.txt

which displays the status like

# grep 'SURVEY_OPTED_IN' /boot/dietpi.txt
SURVEY_OPTED_IN=1

When running

dietpi-servarr_to_ram 1

all found databases are linked to RAM. They can be found at:
/tmp/{sonarr,radarr,lidarr,prowlarr}_db_link

A backup for each linked file is created automatically (and recovered if required), so in case of a system crash only changes from the time of the link are lost. When running the above manually, before shutting down, run

dietpi-servarr_to_ram 0

to store the files back to disk.

To have all databases linked to RAM at boot and stored back to disk on shutdown automatically, execute

dietpi-servarr_to_ram enable

resp.

dietpi-servarr_to_ram disable

to stop this automatism.

To further reduce the risk of lost info/settings, the following command updates the backups:

dietpi-servarr_to_ram 2

This can also be done per program, e.g. to only update the Sonarr database backup:

dietpi-servarr_to_ram 2 sonarr

This allows the program itself to do this as well. Within Sonarr, Radarr, Lidarr and Prowlarr web UI configured custom scripts can be run by the user on certain triggers, e.g. when a download has been finished.
For this the following steps are conducted:

1. Open the web UI, e.g. for Sonarr http://<your.IP>:8989
2. Go to Settings
3. Select the tab Connect
4. Select + to add a new notification
5. Select Custom Script
6. Give it some name and select the trigger sliders as desired, On Download makes most sense here since after download the disk is spinning already and the info is important enough to assure it is preserved even on system crash.
7. As path type: /boot/dietpi/misc/dietpi-servarr_to_ram
8. As arguments enter e.g. 2 sonarr for Sonarr, 2 radarr for Radarr etc.
9. Select Test to verify you entered everything correctly, then Save