Something I don't yet understand.
My systemd system.conf looks like this:Restart watchdog is set to 60. This means, that if during reboot something happens, the Watchdog should kick in.
But this is clearly not the case. Do I need to activate the watchdog separately on Raspberry Pi somehow? Or does the Raspberry Pi watchdog have issues with a value of 60?
My systemd system.conf looks like this:
Code:
[Manager]#LogLevel=info#LogTarget=journal-or-kmsg#LogColor=yes#LogLocation=no#LogTime=no#DumpCore=yes#ShowStatus=yes#CrashChangeVT=no#CrashShell=no#CrashReboot=no#CtrlAltDelBurstAction=reboot-force#CPUAffinity=#NUMAPolicy=default#NUMAMask=#RuntimeWatchdogSec=off#RuntimeWatchdogPreSec=off#RuntimeWatchdogPreGovernor=RebootWatchdogSec=60#KExecWatchdogSec=off#WatchdogDevice=#CapabilityBoundingSet=#NoNewPrivileges=no#SystemCallArchitectures=#TimerSlackNSec=#StatusUnitFormat=description#DefaultTimerAccuracySec=1min#DefaultStandardOutput=journal#DefaultStandardError=inherit#DefaultTimeoutStartSec=90s#DefaultTimeoutStopSec=90s#DefaultTimeoutAbortSec=#DefaultDeviceTimeoutSec=90s#DefaultRestartSec=100ms#DefaultStartLimitIntervalSec=10s#DefaultStartLimitBurst=5#DefaultEnvironment=#DefaultCPUAccounting=yes#DefaultIOAccounting=no#DefaultIPAccounting=no#DefaultMemoryAccounting=yes#DefaultTasksAccounting=yes#DefaultTasksMax=15%#DefaultLimitCPU=#DefaultLimitFSIZE=#DefaultLimitDATA=#DefaultLimitSTACK=#DefaultLimitCORE=#DefaultLimitRSS=#DefaultLimitNOFILE=1024:524288#DefaultLimitAS=#DefaultLimitNPROC=#DefaultLimitMEMLOCK=8M#DefaultLimitLOCKS=#DefaultLimitSIGPENDING=#DefaultLimitMSGQUEUE=#DefaultLimitNICE=#DefaultLimitRTPRIO=#DefaultLimitRTTIME=#DefaultMemoryPressureThresholdSec=200ms#DefaultMemoryPressureWatch=auto#DefaultOOMPolicy=stop#DefaultSmackProcessLabel=#ReloadLimitIntervalSec=#ReloadLimitBurst=But this is clearly not the case. Do I need to activate the watchdog separately on Raspberry Pi somehow? Or does the Raspberry Pi watchdog have issues with a value of 60?
Statistics: Posted by batwing — Thu Jan 30, 2025 12:21 am