add config option to disable logging into the daemon log file
|Target version:||1.2 (Stable)|
changes behavior, needs to be discussed.
-------- Original Message -------- Subject: [Nagios-devel] use_syslog patch Date: Fri, 5 Jun 2009 11:37:41 -0600 From: Steven D. Morrey <firstname.lastname@example.org> Reply-To: Nagios Developers List <email@example.com> To: firstname.lastname@example.org <email@example.com> Hi Everyone, The patch attached adds another option to use_syslog. This option is 2 and will cause it to log to syslog only, thus preventing nagios.log from being written. Beware: Setting this option will break ANYTHING that requires the log to function this includes history browsing, so use it at your own risk. I have created 2 versions, one for nagios-2.12 and one for nagios-3x (todays cvs) Enjoy! Sincerely, Steve
#2 Updated by Meier almost 5 years ago
since we already have the syslog facility, we need to force attention in changing use_syslog sth other than 0 or 1 which could cause confusion.
it might be good to just add a new config option "no_daemon_log=1" if icinga.log shouldn't be written.
i don't see why this should cause confusion, also it does not affect any previous configurations. before you implement more and more config options the config parser should be revamped.
i would apply this patch.
#3 Updated by dnsmichi almost 5 years ago
- Category changed from Other to Configuration
- Status changed from Feedback to New
- Priority changed from Low to Normal
you are right on that, it does not really matter in this regard.
but i would consider setting the default config option to 2 for future releases (which is incompatible to older versions).
#5 Updated by elagon almost 5 years ago
I really prefer the idea of "no_daemon_log=1"
If I will modify your commit with this option instead will it be ok with you?
The think I don't like very much is using the boolean variable "use_syslog" for more than one it's yes|no value, I think users will be confused about this.
#11 Updated by dnsmichi over 4 years ago
- Status changed from Resolved to Assigned
tests and output? during testing period before a release this needs to be extensively clarified for the rest, in order to adapt test cases.
this is a feature, not a bugfix - can this run into 1.0.3?
in that case, features require a docs issue too.
#12 Updated by elagon over 4 years ago
Sorry, forgot about that.
I tested it on Ubuntu Server 8.04 32bit and Ubuntu Desktop 10.04 32bit.
I think we can postpone it, it's not a feature essential for 1.0.3
For the doc issue I always prefere to see the commit in master first because it can be refused and in that case the doc issue was done for nothing :)