On 04/10/2014 02:36 PM, Sven Kieske wrote:
Am 10.04.2014 12:04, schrieb Dan Kenigsberg:
> Could you present (here, or on bugzilla) your use case for another
> syslog service? Which one? Or do you want to turn it off completely?
I'll do both (here and on BZ):
Usecase:
Well utilize existing log infrastructure which doesn't use
rsyslog, perhaps?
e.g. syslog-ng
furthermore: vdsms logging is configured via /etc/vdsm/logger.conf
and uses the python module logging:
https://docs.python.org/2/library/logging.html
this module is pretty cool, it allows you to redirect
your logging basically to wherever you like, including syslog services
or files, whatever.
so why restrict this builtin feature by adding a hard dependency
to a specific logging service?
I know it's done because it's built on red hat linux where rsyslog
is the default, and I don't want to say rsyslog is bad, it's just
not used by everybody.
As I understand there is work be done to port vdsm and engine
to different distros like debian/ubuntu and gentoo.
If you really want to port your software, keep it portable.
This means in the first place don't introduce dependencies
which aren't absolutely necessary.
wouldn't that just be a dependency change for the package for the other
distro's? its not like they will use the rhel spec anyway?
This one isn't really necessary.
I can report to you that e.g. syslog-ng handles vdsm logs
well. ;)
HTH