-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syslog detection uses hardcoded paths #312
Comments
Hello, What Linux distribution/version is this? Thanks, Kris |
A custom one. |
@arvedarved Unfortunately, since your Linux machine is custom (and therefore not on our documented list of supported distributions), you may have to customize some of the OMSAgent support yourself. I would encourage you to create a fork of our repository, alter the differing paths, and build a bundle to install on your machine. |
@arvedarved If you have any other questions, please update this thread; otherwise, this issue will be closed. |
Closing issue due to inactivity |
Currently hardcoded paths are used to find syslog-ng.conf in linux.data
E.g. OMS-Agent expects syslog-ng.conf in /etc/syslog-ng/syslog-ng.conf. On my distribution it is in /etc/syslog-ng.conf Other valid locations are e.g. /usr/local/etc/syslog-ng.conf
Possible solutions:
This also applies to other Paths in linux.data e.g. rsyslog /sudoers configuration files
The text was updated successfully, but these errors were encountered: