LOG_WARNING (or precisely LOG_DEBUG if -v) would be logged.
xenconsoled only actually logs using LOG_ERR and LOG_DEBUG so for the
most part we would have been logging absolutely nothing up until now.
Linux provides a LOG_UPTO macro but I'm not sure how portable that is
so I have opencoded the list of levels.
Do I get some sort of prize for fixing a bug introduced in 2005?
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
xen-unstable changeset: 21814:
91ce0b0953ca
xen-unstable date: Fri Jul 16 12:10:56 2010 +0100
bool is_interactive = false;
int ch;
int syslog_option = LOG_CONS;
- int syslog_mask = LOG_WARNING;
+ int syslog_mask = LOG_MASK(LOG_WARNING)|LOG_MASK(LOG_ERR)|LOG_MASK(LOG_CRIT)|\
+ LOG_MASK(LOG_ALERT)|LOG_MASK(LOG_EMERG);
int opt_ind = 0;
char *pidfile = NULL;
#ifndef __sun__
syslog_option |= LOG_PERROR;
#endif
- syslog_mask = LOG_DEBUG;
+ syslog_mask |= LOG_MASK(LOG_NOTICE)|LOG_MASK(LOG_INFO)| \
+ LOG_MASK(LOG_DEBUG);
break;
case 'i':
is_interactive = true;