Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: use journalctl -t fapolicyd to get fapolicyd log messages
Cause: On EL10, using `journalctl -u fapolicyd` does not work - sometime during fapolicyd startup, the `UNIT` field is dropped from the journald log entries, which is what `-u` uses. Consequence: The fapolicyd role never sees the journald log message that says fapolicyd is listening for connections. The role fails saying that the trustdb could not be updated. Fix: Use `journalctl -t fapolicyd` instead. This uses the journald field SYSLOG_IDENTIFIER which is stable and works on all supported platforms. Result: The role can tell when fapolicyd is up and listening. The role can successfully update the trust db. Signed-off-by: Rich Megginson <[email protected]>
- Loading branch information