You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since refactoring the services the stop case in armbian-hardware-monitor has become useless since never executed.
I tried to nail this down some time ago but to no avail. systemd NOOB still.
Related: To get nicer log output it would be great if armbian-hardware-monitor could wait for firstrun and resize2fs services to finish before starting to log. Also no idea how to achieve this.
The text was updated successfully, but these errors were encountered:
The armbian-hardware-monitor script has a start and a stop case. But the script will never be called on shutdown. I don't think it's needed to understand anything inside the script(s) since it boils down to how systemd handles such stuff (keeping the script active or not, executing it on shutdown/reboot).
Okay so according to the systemd.service docs, the unit file for the armbian-hardware-monitor service does the right thing and the shutdown cleanup steps should be happening.
Since the job is a oneshot, and has the RemainAfterExit flag is true, the ExecStop command is supposed to be executed.
The reality is that I'm not seeing ###shutdown logged anywhere in /var/log/armbian-hardware-monitor.log to indicate the stop command is actually happening...
I'm going to rename issue for clarity now that i understand it.
lanefu
changed the title
Monitoring issues
assure armbian-hardware-monitor starts after armbian-firmboot and excutes cleanup steps on system shutdown.
Dec 19, 2018
Since refactoring the services the
stop
case in armbian-hardware-monitor has become useless since never executed.I tried to nail this down some time ago but to no avail.
systemd
NOOB still.Related: To get nicer log output it would be great if
armbian-hardware-monitor
could wait forfirstrun
andresize2fs
services to finish before starting to log. Also no idea how to achieve this.The text was updated successfully, but these errors were encountered: