change default auto-quit duration, fix connections right border

Author: saltedlolly

diginode-setup.sh

@@ -509,7 +509,7 @@ if [ ! -f "$DGNT_SETTINGS_FILE" ]; then
 
     # OTHER SETTINGS
     DGB_MAX_CONNECTIONS=150
-    SM_AUTO_QUIT=20
+    SM_AUTO_QUIT=1440
     SM_DISPLAY_BALANCE=YES
     SM_DISPLAY_MAINNET_MEMPOOL=YES
     SM_DISPLAY_TESTNET_MEMPOOL=YES
@@ -689,10 +689,12 @@ DGB_DATA_LOCATION=$DGB_DATA_LOCATION
 # (Note: If a digibyte.conf file already exists that sets the maxconnections already, the value here will be ignored)
 DGB_MAX_CONNECTIONS=$DGB_MAX_CONNECTIONS
 
-# Stop the DigiNode Dashboard automatically if it is left running. The default is 20 minutes.
+# Stop the DigiNode Dashboard automatically if it is left running. The default is 1440 minutes.
 # To avoid putting unnecessary strain on your device, it is inadvisable to run DigiNode Dashboard for
 # long periods. Enter the number of minutes before it exits automatically, or set to 0 to run indefinitely.
-# e.g. To stop after 1 hour enter: 60 
+# Note: Running indefinitely is nor reccomended if you frequently lose connection to your node since the
+# old dashboards will be left running in the background. It is always reccomnded to set a fixed limit.
+# e.g. To stop after 24 hours enter: 1440 
 SM_AUTO_QUIT=$SM_AUTO_QUIT
 
 # Choose whether to display the current wallet balance in the DigiNode Dashboard. (Specify either YES or NO.)

diginode.sh

@@ -3555,7 +3555,7 @@ if [ "$DGB2_STATUS" = "running" ] && [ "$DGB_DUAL_NODE" = "YES" ]; then
     DGB2_CONNECTIONS_MSG="Warning: Low Connections!"
   fi
   if [ $DGB2_CONNECTIONS -ge 9 ]; then
-    DGB2_CONNECTIONS_MSG="Maximum: $DGB2_MAXCONNECTIONS"
+    DGB2_CONNECTIONS_MSG="Max: $DGB2_MAXCONNECTIONS"
   fi
 
   # Lookup incoming and outgoing connections
@@ -4566,7 +4566,7 @@ if [ "$terminal_resized" = "yes" ] || [ "$STARTUP_LOOP" = true ]; then
 
     # Calculate the column widths based on terminal width
     col_width_dgb_connections_low=$((term_width - 38 - 29 - 3 - 2)) 
-    col_width_dgb_connections_max=$((term_width - 38 - 29 - 3 - 2))
+    col_width_dgb_connections_max=$((term_width - 38 - 13 - 3 - 2))
     col_width_dgb_blockheight_long=$((term_width - 39 - 32 - 3 - 2)) 
     col_width_dgb_blockheight=$((term_width - 38 - 19 - 3 - 2)) 
     col_width_dgb_mempool=$((term_width - 38 - 30 - 3 - 2)) 
@@ -4921,7 +4921,7 @@ if [ "$DGB_STATUS" = "running" ]; then # Only display if primary DigiByte Node i
     if [ $DGB_CONNECTIONS -le 8 ]; then
         printf " ║ DIGIBYTE NODE  ║    CONNECTIONS ║  " && printf "%-${col_width_dgb_connections_low}s %29s %-3s\n" "$DGB_CONNECTIONS Peers  ( In: $DGB_PEERS_IN | Out: $DGB_PEERS_OUT )" "[ ${txtbred}$DGB_CONNECTIONS_MSG${txtrst} ]" " ║ "
     else
-        printf " ║ DIGIBYTE NODE  ║    CONNECTIONS ║  " && printf "%-${col_width_dgb_connections_max}s %29s %-3s\n" "$DGB_CONNECTIONS Peers  ( In: $DGB_PEERS_IN | Out: $DGB_PEERS_OUT )" "[ $DGB_CONNECTIONS_MSG ]" " ║ "
+        printf " ║ DIGIBYTE NODE  ║    CONNECTIONS ║  " && printf "%-${col_width_dgb_connections_max}s %13s %-3s\n" "$DGB_CONNECTIONS Peers  ( In: $DGB_PEERS_IN | Out: $DGB_PEERS_OUT )" "[ $DGB_CONNECTIONS_MSG ]" " ║ "
     fi
     # Choose the correct network chain border
     if [ "$dgb_chain_caps" = "MAINNET" ]; then
@@ -5054,7 +5054,7 @@ if [ "$DGB_DUAL_NODE" = "YES" ]; then
         if [ $DGB2_CONNECTIONS -le 8 ]; then
             printf " ║ DIGIBYTE NODE  ║    CONNECTIONS ║  " && printf "%-${col_width_dgb_connections_low}s %29s %-3s\n" "$DGB2_CONNECTIONS Nodes  ( In: $DGB2_PEERS_IN | Out: $DGB2_PEERS_OUT )" "[ ${txtbred}$DGB2_CONNECTIONS_MSG${txtrst} ]" " ║ "
         else
-            printf " ║ DIGIBYTE NODE  ║    CONNECTIONS ║  " && printf "%-${col_width_dgb_connections_max}s %29s %-3s\n" "$DGB2_CONNECTIONS Nodes  ( In: $DGB2_PEERS_IN | Out: $DGB2_PEERS_OUT )" "[ $DGB2_CONNECTIONS_MSG ]" " ║ "
+            printf " ║ DIGIBYTE NODE  ║    CONNECTIONS ║  " && printf "%-${col_width_dgb_connections_max}s %13s %-3s\n" "$DGB2_CONNECTIONS Nodes  ( In: $DGB2_PEERS_IN | Out: $DGB2_PEERS_OUT )" "[ $DGB2_CONNECTIONS_MSG ]" " ║ "
         fi
         # Display the TESTNET network chain border
         echo "$sm_row_02_testnet" # "║" "(TESTNET)" "╠" "═" "╬" "═" "╣"

docs/release_notes.md

@@ -1,11 +1,13 @@
 ## DigiNode Tools Release Notes
 
 DigiNode Tools v0.11.1 - 2025-04-xx
-- Coming Soon
+- Change: Default auto quit duration for the DigiNode Dashboard has been changed to 24 hours (1440 minutes).
+- Fix: When running a Dual Node, the Testnet listening port now displays correctly in the Dashboard while the node is starting up. (It was blank before)
+- Fix: Right border for Connections row in dashboard now fits better.
 
 DigiNode Tools v0.11.0 - 2025-04-19
 - New: DigiNode Dashboard now has a brand new port tester built for DigiNode Tools. It can test nodes at IPv4, IPv6 and onion addresses. The port tester is also available for anyone to use at: https://diginode.tools/digibyte-port-tester/
-- New: DigiNode Dashboard now optionally displays the mempool data for each node. By default, Mempool data is displayed whenever transactions enter the mempool and is hidden if there are no transactions seen for 30 seconds. This way mempool data is only shown when there are transactions occurring, which helps keep the testnet mempool data hidden when the network is not being used. You can enable/disable displaying the mempool data by editing the variables SM_DISPLAY_MAINNET_MEMPOOL and SM_DISPLAY_TESTNET_MEMPOOL in diginode.settings. (Enter ```diginode --settings```). SM_MEMPOOL_DISPLAY_TIMEOUT can be used to set the timeout duration.
+- New: DigiNode Dashboard now optionally displays the mempool data for each node. By default, Mempool data is displayed whenever transactions enter the mempool and is hidden if there are no transactions seen for 30 seconds. This way mempool data is shown only when there is mempool data to show. You can enable/disable displaying the mempool data by editing the variables SM_DISPLAY_MAINNET_MEMPOOL and SM_DISPLAY_TESTNET_MEMPOOL in diginode.settings. (Enter ```diginode --settings```). SM_MEMPOOL_DISPLAY_TIMEOUT can be used to set the timeout duration.
 - New: DigiNode Dashboard now displays the incoming and outgoing connections for your DigiByte node.
 - Change: peers.dat is now deleted each time you switch between running a Tor node and a clearnet node. This ensures the node starts with a fresh list of peers to connect to.
 - Change: Add message to Dashboard about DigiAsset Core support. Adding support for DigiAsset Core is not possible at this time due to a bug in DigiByte Core v8.22.x.