Syslog detection uses hardcoded paths

[arvedarved]

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:

• Allow specifying location of configuration files as commandline arguments
• Test for common paths

This also applies to other Paths in linux.data e.g. rsyslog /sudoers configuration files

[KrisBash]

Hello,

What Linux distribution/version is this?

Thanks,

Kris

[arvedarved]

A custom one.

[lagalbra]

@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.

[lagalbra]

@arvedarved If you have any other questions, please update this thread; otherwise, this issue will be closed.

[lagalbra]

Closing issue due to inactivity