Even with a proper following distance, sometimes you just can't react fast enough. For those times, there's automatic emergency braking! The "owner" of the trash dump was nowhere to be found for the next several miles so I'm sure they're totally unaware.
Every time that gitea port gets upgraded and I restart, it always fails to actually start and shows no warnings:
[root@thneed]~# service gitea restart
Stopping gitea.
Waiting for PIDS: 91883.
gitea already running? (pid=91883).
[root@thneed]~# service gitea status
gitea is not running.
[root@thneed]~# service gitea start
[root@thneed]~# service gitea status
gitea is running as pid 2673.
The rc script seems reasonable, but clearly it needs to wait for something else before it should attempt the restart.
Does this happen to anyone else?
Running OPNsense 26.1.6_2 (amd64) on a Protectli FW4B.
I have the thermal setting configured to use Intel coretemp kernel module. The numbers on the dashboard disagree with the numbers from the sysctl output.
Right now on the dashboard, it shows 5 numbers:
CPU 0: 47 C
CPU 1: 47 C
CPU 2: 41 C
CPU 3: 39 C
Zone 0: 26.9C
Yet from the CLI at about the same time I see
% sysctl dev.cpu.{0,1,2,3}.temperature hw.acpi.thermal.tz0.temperature
dev.cpu.0.temperature: 40.0C
dev.cpu.1.temperature: 40.0C
dev.cpu.2.temperature: 38.0C
dev.cpu.3.temperature: 36.0C
hw.acpi.thermal.tz0.temperature: 26.9C
Why don't the CPU temperatures align? That's a significant difference. Is the dashboard picking the numbers from a different place? The CPU 0 temps are regularly (but not always) +7 and the CPU 2 are +3 on the dashboard.