Hello Team,
A few years back I heard about a project that would have added functionality to syslog-ng that would have enabled configurability from the command line.
This was the respective PR: https://github.com/balabit/syslog-ng/pull/1326
Since then the PR was closed and part of the functionality provided by the PR has been added to syslog-ng (in https://github.com/balabit/syslog-ng/pull/1605), but not the CLI configurability part.
I personally think that being able to configure syslog-ng through its command line arguments would bear a great potential.
Of course running it with a complex configuration passed in through CLI argument would be infeasible, but with simple, single-purpose logging setups it would prove to be a very powerful tool.
For example when trying to empty a bunch of orphaned disk queue files, it would be very easy to spin up several syslog-ng instances from a script with only slightly differing configuration.
What do you guys think? Do you agree as well that this feature would bear a lot of added value to syslog-ng?
Thanks for sharing your opinions!
Best Regards,
János Szigetvári
--
LinkedIn: linkedin.com/in/janosszigetvari__@__˚V˚
Make the switch to open (source) applications, protocols, formats now:
- windows -> Linux,
iexplore ->
Firefox,
msoffice ->
LibreOffice-
msn -> jabber protocol (Pidgin, Google Talk)
- mp3 ->
ogg,
wmv ->
ogg,
jpg ->
png, doc/
xls/
ppt ->
odt/
ods/
odp