Hello friends, I am thinking about how to monitor not only events from log files, but also those files existence and accessibility (for user running SEC) - in cases, where this is considered to be a problem.
As I saw in the past, these were logged into SEC log file, but higher debug level was required, so it is not suitable for production. There are handful of other options how to monitor it "externally", e.g. via some script, or other monitoring agent, but this is not ultimate solution, as e.g. SELinux may be configured, allowing external script or agent (running under the same user as SEC) to see nad open file for reading, but not SEC (theoretical caveat of such solution). So, has somebody some "best practise" for reliable and production-ready way, how to "self-monitor" log files being accessed by SEC, if: - they exist - they are accessible by SEC ? Thanks in advance. Richard
_______________________________________________ Simple-evcorr-users mailing list Simple-evcorr-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
