The contrib/mc_event_trigger file deployed to the /etc/ras/triggers dir (i.e. TRIGGER_DIR from misc/rasdaemon.env), runs a mc_event_trigger.local file with [ -x ./mc_event_trigger.local ] && . ./mc_event_trigger.local. I'm assuming this mc_event_trigger.local file is intended to be in the same trigger directory as mc_event_trigger, the /etc/ras/triggers dir, but when triggered under systemd only the mc_event_trigger file is ran and not the mc_event_trigger.local.
This happens because mc_event_trigger.local is referenced with a relative path ./ but running under systemd the actual working directory is / and not the expected /etc/ras/triggers dir, e.g.
Snippet added to mc_event_trigger to get the working directory.
Journalctl confirming it was triggered.
Gotten working directory shows as root /.
The
contrib/mc_event_triggerfile deployed to the/etc/ras/triggersdir (i.e.TRIGGER_DIRfrommisc/rasdaemon.env), runs amc_event_trigger.localfile with[ -x ./mc_event_trigger.local ] && . ./mc_event_trigger.local. I'm assuming thismc_event_trigger.localfile is intended to be in the same trigger directory asmc_event_trigger, the/etc/ras/triggersdir, but when triggered under systemd only themc_event_triggerfile is ran and not themc_event_trigger.local.This happens because
mc_event_trigger.localis referenced with a relative path./but running under systemd the actual working directory is/and not the expected/etc/ras/triggersdir, e.g.Snippet added to
mc_event_triggerto get the working directory.Journalctl confirming it was triggered.
Gotten working directory shows as root
/.