summaryrefslogtreecommitdiffstats
path: root/core/modules/system-check/data/opt/openslx/scripts/systemd-system_check
diff options
context:
space:
mode:
authorSimon Rettberg2024-01-29 11:41:58 +0100
committerSimon Rettberg2024-01-29 11:44:37 +0100
commit2ab7082564bb4289b7b95bf1eb7b7a2196a2e615 (patch)
tree7a08215ed2011c103e0aeab5322c1dc6241e2b3f /core/modules/system-check/data/opt/openslx/scripts/systemd-system_check
parentUTF-8 (diff)
downloadmltk-2ab7082564bb4289b7b95bf1eb7b7a2196a2e615.tar.gz
mltk-2ab7082564bb4289b7b95bf1eb7b7a2196a2e615.tar.xz
mltk-2ab7082564bb4289b7b95bf1eb7b7a2196a2e615.zip
[system-check/hardware-stats] Loosen dependencies
For some reason, system-check is ordered before hardware-report, but I can't figure out why. system-check merely generates the warnings to display on the login screen, and hardware-report sends hw data to the boot server. I don't see anything in hardware-report actually depending on anything system-check does. There are some other minor changes, like moving the generation of the json report from hardware-report to hardware-stats, and putting the according python script into a directory named hardware-stats instead of system-check, which might imply it belongs to that module which is wrong.
Diffstat (limited to 'core/modules/system-check/data/opt/openslx/scripts/systemd-system_check')
-rwxr-xr-xcore/modules/system-check/data/opt/openslx/scripts/systemd-system_check2
1 files changed, 1 insertions, 1 deletions
diff --git a/core/modules/system-check/data/opt/openslx/scripts/systemd-system_check b/core/modules/system-check/data/opt/openslx/scripts/systemd-system_check
index 8011498f..d03a8e52 100755
--- a/core/modules/system-check/data/opt/openslx/scripts/systemd-system_check
+++ b/core/modules/system-check/data/opt/openslx/scripts/systemd-system_check
@@ -1,6 +1,6 @@
#!/bin/bash
#
-# Kind of a generic message generation thing. Hooks in /opt/openslx/messages.d
+# Kind of a generic message generation thing. Hooks in /opt/openslx/system-check/hooks.d
# are passed the location of the lightdm warning file on execution. They can either
# ignore it (e.g. for remote logging purposes) or just append tags to that file.
# The tags are defined in /opt/openslx/system-check/tags and will be replaced