setcap:ai:eac91

I have a watchdog.conf file. In it, it shows commented parts on creating new files and where to place them. I have placed them all where they are supposed to be. I can post those internals to you if you would like too. Postfix is supposed to be configured also so that watchdog can send me an email on if something goes wrong. I do not see any emails at the email address that I'm supposed to recieve at, which is ollicopperwolf@outlook.com. . Watchdog status gives me always that it is deactivating ● watchdog.service - Watchdog Service Loaded: loaded (/etc/systemd/system/watchdog.service; enabled; preset: enabled) Active: deactivating (stop-sigterm) since Thu 2024-11-28 18:31:30 CST; 4s ago Process: 33959 ExecStart=/usr/sbin/watchdog -v (code=exited, status=0/SUCCESS) Main PID: 33959 (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 38292) Memory: 580.0K (peak: 1002.7M) CPU: 345ms CGroup: /system.slice/watchdog.service └─33961 /usr/sbin/watchdog -v I also recieve : olli@ollicopperwolf:~$ sudo journalctl -u watchdog | grep -i error Nov 26 23:09:37 Wolf-1 watchdog[2465]: error retry time-out = 60 seconds Nov 28 17:29:27 ollicopperwolf.mynetgear.com watchdog[777318]: error retry time-out = 60 seconds Nov 28 17:31:19 ollicopperwolf.mynetgear.com watchdog[1550]: error retry time-out = 60 seconds Nov 28 17:31:40 ollicopperwolf.mynetgear.com watchdog[4216]: error retry time-out = 60 seconds Nov 28 17:31:40 ollicopperwolf.mynetgear.com watchdog[4216]: test binary /home/olli/.local/bin/watchdog_master_script.sh returned 0 = 'no error' In the watchdog.conf file, it shows at a point on the creation of the master script creation, along with 2 other files that are connected to it be way of commands in the master script. I had to modprobe the hardware and watchdog (not watchdog 0) after a reboot as well, which I'm supposed to have module files that are supposed to do that at boot. So, at first, it wasn't even found. I 'think' I have covered everything and now I will share what is inside of my watchdog.conf file inside of /etc/ on my Linux Mint system. I would like to get this thing working correctly. : I have a watchdog.conf file. In it, it shows commented parts on creating new files and where to place them. I have placed them all where they are supposed to be. I can post those internals to you if you would like too. Postfix is supposed to be configured also so that watchdog can send me an email on if something goes wrong. I do not see any emails at the email address that I'm supposed to recieve at, which is ollicopperwolf@outlook.com. . Watchdog status gives me always that it is deactivating ● watchdog.service - Watchdog Service Loaded: loaded (/etc/systemd/system/watchdog.service; enabled; preset: enabled) Active: deactivating (stop-sigterm) since Thu 2024-11-28 18:31:30 CST; 4s ago Process: 33959 ExecStart=/usr/sbin/watchdog -v (code=exited, status=0/SUCCESS) Main PID: 33959 (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 38292) Memory: 580.0K (peak: 1002.7M) CPU: 345ms CGroup: /system.slice/watchdog.service └─33961 /usr/sbin/watchdog -v I also recieve : olli@ollicopperwolf:~$ sudo journalctl -u watchdog | grep -i error Nov 26 23:09:37 Wolf-1 watchdog[2465]: error retry time-out = 60 seconds Nov 28 17:29:27 ollicopperwolf.mynetgear.com watchdog[777318]: error retry time-out = 60 seconds Nov 28 17:31:19 ollicopperwolf.mynetgear.com watchdog[1550]: error retry time-out = 60 seconds Nov 28 17:31:40 ollicopperwolf.mynetgear.com watchdog[4216]: error retry time-out = 60 seconds Nov 28 17:31:40 ollicopperwolf.mynetgear.com watchdog[4216]: test binary /home/olli/.local/bin/watchdog_master_script.sh returned 0 = 'no error' In the watchdog.conf file, it shows at a point on the creation of the master script creation, along with 2 other files that are connected to it be way of commands in the master script. I had to modprobe the hardware and watchdog (not watchdog 0) after a reboot as well, which I'm supposed to have module files that are supposed to do that at boot. So, at first, it wasn't even found. I 'think' I have covered everything and now I will share what is inside of my watchdog.conf file inside of /etc/ on my Linux Mint system. I would like to get this thing working correctly. : #sudo journalctl -u watchdog - Don't forget to use if there are issues. # ==================================================================== # Configuration for the watchdog daemon. For more information on the # parameters in this file use the command 'man watchdog.conf' # ==================================================================== # =================== The hardware timer settings ==================== # # For this daemon to be effective it really needs some hardware timer # to back up any reboot actions. If you have a server then see if it # has IPMI support. Otherwise for Intel-based machines try the iTCO_wdt # module, otherwise (or if that fails) then see if any of the following # module load and work: # # it87_wdt it8712f_wdt w83627hf_wdt w83877f_wdt w83977f_wdt # # If all else fails then 'softdog' is better than no timer at all! # Or work your way through the modules listed under: # # /lib/modules/`uname -r`/kernel/drivers/watchdog/ # # To see if they load, present /dev/watchdog, and are capable of # resetting the system on time-out. # Uncomment this to use the watchdog device driver access "file". #sudo modprobe iTCO_wdt - If /dev/watchdog0 is missing, create it by using the appropriate kernel module. #sudo modprobe watchdog - Applies hardware module. #Check that the hardware watchdog module is running - ls -l /dev/watchdog0 #Ensure the watchdog configuration file points to the correct device. /dev/watchdog is created by softdog and /dev/watchdog0 is #created by watchdog and iTCO_wdt, which is the hardware module. #watchdog-device = /dev/watchdog0 - 0 represents hardware device. watchdog-device = /dev/watchdog0 #dmesg | grep iTCO_wdt - Checks for hardware watchdog information. #sudo systemctl status watchdog #Memory: 584.0K (peak: 1002.6M) - Shows how much memory watchdog is taking up at the current moment and then the max memory it has taken up at any given moment. #sudo tail -f /var/log/syslog | grep watchdog - Logs for debugging complications. # Uncomment and edit this line for hardware timeout values that differ # from the default of one minute. #watchdog-timeout = 60 watchdog-timeout = 60 # If your watchdog trips by itself when the first timeout interval # elapses then try uncommenting the line below and changing the # value to 'yes'. #watchdog-refresh-use-settimeout = auto # If you have a buggy watchdog device (e.g. some IPMI implementations) # try uncommenting this line and setting it to 'yes'. #watchdog-refresh-ignore-errors = no # ====================== Other system settings ======================== # # Interval between tests. Should be a couple of seconds shorter than # the hardware time-out value. # This is the software heartbeat section. #interval = 1 interval = 25 # The number of intervals skipped before a log message is written (i.e. # a multiplier for 'interval' in terms of syslog messages) #logtick = 1 # Directory for log files (probably best not to change this) #log-dir = /var/log/watchdog # Email address for sending the reboot reason. This needs sendmail to # be installed and properly configured. Maybe you should just enable # syslog forwarding instead? admin = ollicopperwolf@outlook.com # Lock the daemon in to memory as a real-time process. This greatly # decreases the chance that watchdog won't be scheduled before your # machine is really loaded. realtime = yes priority = 1 # ====================== How to handle errors ======================= # # If you have a custom binary/script to handle errors then uncomment # this line and provide the path. For 'v1' test binary files they also # handle error cases. #repair-binary = /usr/sbin/repair #repair-timeout = 60 # The retry-timeout and repair limit are used to handle errors in a # more robust manner. Errors must persist for longer than this to # action a repair or reboot, and if repair-maximum attempts are # made without the test passing a reboot is initiated anyway. #retry-timeout = 60 retry-timeout = 60 #repair-maximum = 1 # Configure the delay on reboot from sending SIGTERM to all processes # and to following up with SIGKILL for any that are ignoring the polite # request to stop. #sigterm-delay = 5 # ====================== User-specified tests ======================== # # Specify the directory for auto-added 'v1' test programs (any executable # found in the 'test-directory should be listed). #test-directory = /etc/watchdog.d # Specify any v0 custom tests here. Multiple lines are permitted, but # having any 'v1' programs/scripts discovered in the 'test-directory' is # the better way. #test-binary = # Specify the time-out value for a test error to be reported. #test-timeout = 60 # ====================== Typical tests =============================== # # Specify any IPv4 numeric addresses to be probed. # NOTE: You should check you have permission to ping any machine before # using it as a test. Also remember if the target goes down then this # machine will reboot as a result! #ping = 172.16.0.1 #ping = 192.168.1.1 #ping = 192.168.3.68 ping = 192.168.4.71 test-binary = /home/olli/.local/bin/watchdog_master_script.sh #For test-binary #Create the watchdog_master_script.sh and place the following in it. #!/bin/bash #/home/olli/.local/bin/watchdog_restart_network.sh #/home/olli/.local/bin/watchdog_send_notification.sh - Needs mailutils downloaded and configured to work. - /etc/postfix/main.cf #Create another script named watchdog_send_notification.sh and place the following in it. ##!/bin/bash #echo "Ping test failed" | mail -s "Watchdog Alert" ollicopperwolf@outlook.com #Create another script named watchdog_restart_network.sh with the following in it. ##!/bin/bash #systemctl restart networking #If there is any error 127 ever returned, it indicates that the command or script could not be found or executed. # Set the number of ping attempts in each 'interval' of time. Default # is 3 and it completes on the first successful ping. # NOTE: Round-trip delay has to be less than 'interval' / 'ping-count' # for test success, but this is unlikely to be exceeded except possibly # on satellite links (very unlikely case!). #ping-count = 3 ping-count = 1 ##Heartbeat - heartbeat IS a file. #heartbeat-file = /var/run/watchdog/heartbeat #ls -l /var/run/watchdog/heartbeat # Specify any network interface to be checked for activity. #interface = eth0 interface = eno1 #interface = utun420 # Specify any files to be checked for presence, and if desired, checked # that they have been updated more recently than 'change' seconds. #file = /var/log/syslog #change = 1407 #sudo chmod 644 /mnt/Texts/Family.txt #sudo chmod 644 /mnt/Texts/Linux Tweaks.txt #sudo chown root:root /mnt/Texts/Family.txt #sudo chown root:root /mnt/Texts/Linux Tweaks.txt file = /mnt/Backups/Family.txt file = /mnt/Backups/Linux Tweaks.txt file = /mnt/Backups/Local Furries of Crestview.txt file = /mnt/Backups/LinksHTM/Links.htm file = /mnt/Backups/Watchdog/watchdog.conf file = /mnt/Backups/Watchdog/postfix/main.cf file = /mnt/Backups/Watchdog/watchdog_master_script.sh # Uncomment to enable load average tests for 1, 5 and 15 minute # averages. Setting one of these values to '0' disables it. These # values will hopefully never reboot your machine during normal use # (if your machine is really hung, the loadavg will go much higher # than 25 in most cases). #Just examples, so can set whatever you want up to 24. Numbers need to meet the uptime command's 3 outputs and not be under #max-load-1 = 24 #max-load-5 = 18 #max-load-15 = 12 max-load-1 = 3 max-load-5 = 2.5 max-load-15 = 2.0 # Check available memory on the machine. # # The min-memory check is a passive test from reading the file # /proc/meminfo and computed from MemFree + Buffers + Cached # If this is below a few tens of MB you are likely to have problems. # # The allocatable-memory is an active test checking it can be paged # in to use. # # Maximum swap should be based on normal use, probably a large part of # available swap but paging 1GB of swap can take tens of seconds. # # NOTE: This is the number of pages, to get the real size, check how # large the pagesize is on your machine (typically 4kB for x86 hardware). #min-memory = 1 - Ensures a minimum amount of free memory is always available. - Doesn't stack with allocatable. #allocatable-memory = 1 - Ensures the system can allocate a specified amount of memory. This setting helps #prevent the system from running out of memory, which could lead to crashes or other issues. #For a system with 32GB of RAM, a good starting point for allocatable-memory would be around 1GB (256,000 pages, since each page is 4KB). #Effectively ensures that there is always at least 2GB available for both free and allocatable memory. #max-swap = 512 - Set this to a value that is higher than your typical usage but still reasonable. For example, 512 pages (2MB) / 2 = 1MB. min-memory = 256000 allocatable-memory = 256000 max-swap = 256 # Check for over-temperature. Typically the temperature-sensor is a # 'virtual file' under /sys and it contains the temperature in # milli-Celsius. Usually these are generated by the 'sensors' package, # but take care as device enumeration may not be fixed. #temperature-sensor = #max-temperature = 90 temperature-sensor = /sys/class/hwmon/hwmon0/temp1_input max-temperature = 80 # Check for a running process/daemon by its PID file. For example, # check if rsyslogd is still running by enabling the following line: #pidfile = /var/run/rsyslogd.pid #Apply this if there is an error opening sockets. #sudo setcap cap_net_raw,cap_net_admin=eip /usr/sbin/watchdog

Questions that are answered by this command:

• I have a watchdog.conf file. In it, it shows commented parts on creating new files and where to place them. I have placed them all where they are supposed to be. I can post those internals to you if you would like too. Postfix is supposed to be configured also so that watchdog can send me an email on if something goes wrong. I do not see any emails at the email address that I'm supposed to recieve at, which is ollicopperwolf@outlook.com. . Watchdog status gives me always that it is deactivating ● watchdog.service - Watchdog Service Loaded: loaded (/etc/systemd/system/watchdog.service; enabled; preset: enabled) Active: deactivating (stop-sigterm) since Thu 2024-11-28 18:31:30 CST; 4s ago Process: 33959 ExecStart=/usr/sbin/watchdog -v (code=exited, status=0/SUCCESS) Main PID: 33959 (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 38292) Memory: 580.0K (peak: 1002.7M) CPU: 345ms CGroup: /system.slice/watchdog.service └─33961 /usr/sbin/watchdog -v I also recieve : olli@ollicopperwolf:~$ sudo journalctl -u watchdog | grep -i error Nov 26 23:09:37 Wolf-1 watchdog[2465]: error retry time-out = 60 seconds Nov 28 17:29:27 ollicopperwolf.mynetgear.com watchdog[777318]: error retry time-out = 60 seconds Nov 28 17:31:19 ollicopperwolf.mynetgear.com watchdog[1550]: error retry time-out = 60 seconds Nov 28 17:31:40 ollicopperwolf.mynetgear.com watchdog[4216]: error retry time-out = 60 seconds Nov 28 17:31:40 ollicopperwolf.mynetgear.com watchdog[4216]: test binary /home/olli/.local/bin/watchdog_master_script.sh returned 0 = 'no error' In the watchdog.conf file, it shows at a point on the creation of the master script creation, along with 2 other files that are connected to it be way of commands in the master script. I had to modprobe the hardware and watchdog (not watchdog 0) after a reboot as well, which I'm supposed to have module files that are supposed to do that at boot. So, at first, it wasn't even found. I 'think' I have covered everything and now I will share what is inside of my watchdog.conf file inside of /etc/ on my Linux Mint system. I would like to get this thing working correctly. : I have a watchdog.conf file. In it, it shows commented parts on creating new files and where to place them. I have placed them all where they are supposed to be. I can post those internals to you if you would like too. Postfix is supposed to be configured also so that watchdog can send me an email on if something goes wrong. I do not see any emails at the email address that I'm supposed to recieve at, which is ollicopperwolf@outlook.com. . Watchdog status gives me always that it is deactivating ● watchdog.service - Watchdog Service Loaded: loaded (/etc/systemd/system/watchdog.service; enabled; preset: enabled) Active: deactivating (stop-sigterm) since Thu 2024-11-28 18:31:30 CST; 4s ago Process: 33959 ExecStart=/usr/sbin/watchdog -v (code=exited, status=0/SUCCESS) Main PID: 33959 (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 38292) Memory: 580.0K (peak: 1002.7M) CPU: 345ms CGroup: /system.slice/watchdog.service └─33961 /usr/sbin/watchdog -v I also recieve : olli@ollicopperwolf:~$ sudo journalctl -u watchdog | grep -i error Nov 26 23:09:37 Wolf-1 watchdog[2465]: error retry time-out = 60 seconds Nov 28 17:29:27 ollicopperwolf.mynetgear.com watchdog[777318]: error retry time-out = 60 seconds Nov 28 17:31:19 ollicopperwolf.mynetgear.com watchdog[1550]: error retry time-out = 60 seconds Nov 28 17:31:40 ollicopperwolf.mynetgear.com watchdog[4216]: error retry time-out = 60 seconds Nov 28 17:31:40 ollicopperwolf.mynetgear.com watchdog[4216]: test binary /home/olli/.local/bin/watchdog_master_script.sh returned 0 = 'no error' In the watchdog.conf file, it shows at a point on the creation of the master script creation, along with 2 other files that are connected to it be way of commands in the master script. I had to modprobe the hardware and watchdog (not watchdog 0) after a reboot as well, which I'm supposed to have module files that are supposed to do that at boot. So, at first, it wasn't even found. I 'think' I have covered everything and now I will share what is inside of my watchdog.conf file inside of /etc/ on my Linux Mint system. I would like to get this thing working correctly. : #sudo journalctl -u watchdog - Don't forget to use if there are issues. # ==================================================================== # Configuration for the watchdog daemon. For more information on the # parameters in this file use the command 'man watchdog.conf' # ==================================================================== # =================== The hardware timer settings ==================== # # For this daemon to be effective it really needs some hardware timer # to back up any reboot actions. If you have a server then see if it # has IPMI support. Otherwise for Intel-based machines try the iTCO_wdt # module, otherwise (or if that fails) then see if any of the following # module load and work: # # it87_wdt it8712f_wdt w83627hf_wdt w83877f_wdt w83977f_wdt # # If all else fails then 'softdog' is better than no timer at all! # Or work your way through the modules listed under: # # /lib/modules/`uname -r`/kernel/drivers/watchdog/ # # To see if they load, present /dev/watchdog, and are capable of # resetting the system on time-out. # Uncomment this to use the watchdog device driver access "file". #sudo modprobe iTCO_wdt - If /dev/watchdog0 is missing, create it by using the appropriate kernel module. #sudo modprobe watchdog - Applies hardware module. #Check that the hardware watchdog module is running - ls -l /dev/watchdog0 #Ensure the watchdog configuration file points to the correct device. /dev/watchdog is created by softdog and /dev/watchdog0 is #created by watchdog and iTCO_wdt, which is the hardware module. #watchdog-device = /dev/watchdog0 - 0 represents hardware device. watchdog-device = /dev/watchdog0 #dmesg | grep iTCO_wdt - Checks for hardware watchdog information. #sudo systemctl status watchdog #Memory: 584.0K (peak: 1002.6M) - Shows how much memory watchdog is taking up at the current moment and then the max memory it has taken up at any given moment. #sudo tail -f /var/log/syslog | grep watchdog - Logs for debugging complications. # Uncomment and edit this line for hardware timeout values that differ # from the default of one minute. #watchdog-timeout = 60 watchdog-timeout = 60 # If your watchdog trips by itself when the first timeout interval # elapses then try uncommenting the line below and changing the # value to 'yes'. #watchdog-refresh-use-settimeout = auto # If you have a buggy watchdog device (e.g. some IPMI implementations) # try uncommenting this line and setting it to 'yes'. #watchdog-refresh-ignore-errors = no # ====================== Other system settings ======================== # # Interval between tests. Should be a couple of seconds shorter than # the hardware time-out value. # This is the software heartbeat section. #interval = 1 interval = 25 # The number of intervals skipped before a log message is written (i.e. # a multiplier for 'interval' in terms of syslog messages) #logtick = 1 # Directory for log files (probably best not to change this) #log-dir = /var/log/watchdog # Email address for sending the reboot reason. This needs sendmail to # be installed and properly configured. Maybe you should just enable # syslog forwarding instead? admin = ollicopperwolf@outlook.com # Lock the daemon in to memory as a real-time process. This greatly # decreases the chance that watchdog won't be scheduled before your # machine is really loaded. realtime = yes priority = 1 # ====================== How to handle errors ======================= # # If you have a custom binary/script to handle errors then uncomment # this line and provide the path. For 'v1' test binary files they also # handle error cases. #repair-binary = /usr/sbin/repair #repair-timeout = 60 # The retry-timeout and repair limit are used to handle errors in a # more robust manner. Errors must persist for longer than this to # action a repair or reboot, and if repair-maximum attempts are # made without the test passing a reboot is initiated anyway. #retry-timeout = 60 retry-timeout = 60 #repair-maximum = 1 # Configure the delay on reboot from sending SIGTERM to all processes # and to following up with SIGKILL for any that are ignoring the polite # request to stop. #sigterm-delay = 5 # ====================== User-specified tests ======================== # # Specify the directory for auto-added 'v1' test programs (any executable # found in the 'test-directory should be listed). #test-directory = /etc/watchdog.d # Specify any v0 custom tests here. Multiple lines are permitted, but # having any 'v1' programs/scripts discovered in the 'test-directory' is # the better way. #test-binary = # Specify the time-out value for a test error to be reported. #test-timeout = 60 # ====================== Typical tests =============================== # # Specify any IPv4 numeric addresses to be probed. # NOTE: You should check you have permission to ping any machine before # using it as a test. Also remember if the target goes down then this # machine will reboot as a result! #ping = 172.16.0.1 #ping = 192.168.1.1 #ping = 192.168.3.68 ping = 192.168.4.71 test-binary = /home/olli/.local/bin/watchdog_master_script.sh #For test-binary #Create the watchdog_master_script.sh and place the following in it. #!/bin/bash #/home/olli/.local/bin/watchdog_restart_network.sh #/home/olli/.local/bin/watchdog_send_notification.sh - Needs mailutils downloaded and configured to work. - /etc/postfix/main.cf #Create another script named watchdog_send_notification.sh and place the following in it. ##!/bin/bash #echo "Ping test failed" | mail -s "Watchdog Alert" ollicopperwolf@outlook.com #Create another script named watchdog_restart_network.sh with the following in it. ##!/bin/bash #systemctl restart networking #If there is any error 127 ever returned, it indicates that the command or script could not be found or executed. # Set the number of ping attempts in each 'interval' of time. Default # is 3 and it completes on the first successful ping. # NOTE: Round-trip delay has to be less than 'interval' / 'ping-count' # for test success, but this is unlikely to be exceeded except possibly # on satellite links (very unlikely case!). #ping-count = 3 ping-count = 1 ##Heartbeat - heartbeat IS a file. #heartbeat-file = /var/run/watchdog/heartbeat #ls -l /var/run/watchdog/heartbeat # Specify any network interface to be checked for activity. #interface = eth0 interface = eno1 #interface = utun420 # Specify any files to be checked for presence, and if desired, checked # that they have been updated more recently than 'change' seconds. #file = /var/log/syslog #change = 1407 #sudo chmod 644 /mnt/Texts/Family.txt #sudo chmod 644 /mnt/Texts/Linux Tweaks.txt #sudo chown root:root /mnt/Texts/Family.txt #sudo chown root:root /mnt/Texts/Linux Tweaks.txt file = /mnt/Backups/Family.txt file = /mnt/Backups/Linux Tweaks.txt file = /mnt/Backups/Local Furries of Crestview.txt file = /mnt/Backups/LinksHTM/Links.htm file = /mnt/Backups/Watchdog/watchdog.conf file = /mnt/Backups/Watchdog/postfix/main.cf file = /mnt/Backups/Watchdog/watchdog_master_script.sh # Uncomment to enable load average tests for 1, 5 and 15 minute # averages. Setting one of these values to '0' disables it. These # values will hopefully never reboot your machine during normal use # (if your machine is really hung, the loadavg will go much higher # than 25 in most cases). #Just examples, so can set whatever you want up to 24. Numbers need to meet the uptime command's 3 outputs and not be under #max-load-1 = 24 #max-load-5 = 18 #max-load-15 = 12 max-load-1 = 3 max-load-5 = 2.5 max-load-15 = 2.0 # Check available memory on the machine. # # The min-memory check is a passive test from reading the file # /proc/meminfo and computed from MemFree + Buffers + Cached # If this is below a few tens of MB you are likely to have problems. # # The allocatable-memory is an active test checking it can be paged # in to use. # # Maximum swap should be based on normal use, probably a large part of # available swap but paging 1GB of swap can take tens of seconds. # # NOTE: This is the number of pages, to get the real size, check how # large the pagesize is on your machine (typically 4kB for x86 hardware). #min-memory = 1 - Ensures a minimum amount of free memory is always available. - Doesn't stack with allocatable. #allocatable-memory = 1 - Ensures the system can allocate a specified amount of memory. This setting helps #prevent the system from running out of memory, which could lead to crashes or other issues. #For a system with 32GB of RAM, a good starting point for allocatable-memory would be around 1GB (256,000 pages, since each page is 4KB). #Effectively ensures that there is always at least 2GB available for both free and allocatable memory. #max-swap = 512 - Set this to a value that is higher than your typical usage but still reasonable. For example, 512 pages (2MB) / 2 = 1MB. min-memory = 256000 allocatable-memory = 256000 max-swap = 256 # Check for over-temperature. Typically the temperature-sensor is a # 'virtual file' under /sys and it contains the temperature in # milli-Celsius. Usually these are generated by the 'sensors' package, # but take care as device enumeration may not be fixed. #temperature-sensor = #max-temperature = 90 temperature-sensor = /sys/class/hwmon/hwmon0/temp1_input max-temperature = 80 # Check for a running process/daemon by its PID file. For example, # check if rsyslogd is still running by enabling the following line: #pidfile = /var/run/rsyslogd.pid #Apply this if there is an error opening sockets. #sudo setcap cap_net_raw,cap_net_admin=eip /usr/sbin/watchdog?