Date: Mon, 29 Jan 2001 18:04:59 -0500 From: Andrew J Caines <A.J.Caines@altavista.net> To: freebsd-stable@FreeBSD.ORG Cc: Tony Byrne <tony@nua.ie> Subject: Re: syslogd throwing a hissy fit Message-ID: <20010129180459.D372@hal9000.bsdonline.org> In-Reply-To: <alma7t4noj9u417v4t026fuuffkoflhf75@4ax.com>; from tony@nua.ie on Mon, Jan 29, 2001 at 12:00:45PM %2B0000 References: <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> <s7hu6torq3c79usoqpgig3b56gg9d5n6jr@4ax.com> <20010124223705.A92362@gosset.maths.tcd.ie> <5qou6tkiba9jk6nbjepe9hn2g45hq560ep@4ax.com> <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> <s7hu6torq3c79usoqpgig3b56gg9d5n6jr@4ax.com> <20010124223705.A92362@gosset.maths.tcd.ie> <20010128162429.A412@hal9000.bsdonline.org> <alma7t4noj9u417v4t026fuuffkoflhf75@4ax.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Folks, Is anyone running STABLE cvsup'ed in the last couple of weeks with syslogd logging console.info messages without error? Tony, Thanks for submitting the PR. I'd like to see it if you don't mind digging up the reference. > *.info;kern.debug;cron.notice;mail.crit;local2.none /dev/console > Remove '*.info;' from the beginning of the entry and restart syslogd. I switched it to *.notice and fired up syslogd, which did exactly as you predicted: > This should avoid the trigger for this particular problem. I'd neglected to consider the console facility being matched by the wildcard. This narrows down the problem to that is what is causing the console.info messages. -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@altavista.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010129180459.D372>