From owner-freebsd-questions Sun Jul 18 11:37:55 1999 Delivered-To: freebsd-questions@freebsd.org Received: from twwells.com (twwells.com [209.118.236.57]) by hub.freebsd.org (Postfix) with SMTP id 011FD14CD4 for ; Sun, 18 Jul 1999 11:37:41 -0700 (PDT) (envelope-from bill@twwells.com) Received: from bill by twwells.com with local (Exim 1.71 #2) id 115vml-00089S-00; Sun, 18 Jul 1999 14:35:39 -0400 Subject: Re: Why is this code in syslogd.c? To: andre.albsmeier@mchp.siemens.de (Andre Albsmeier) Date: Sun, 18 Jul 1999 14:35:39 -0400 (EDT) Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <19990718194853.A29020@internal> from "Andre Albsmeier" at Jul 18, 99 07:48:53 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Content-Length: 648 Message-Id: From: "T. William Wells" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 18-Jul-1999 at 13:18:01 -0400, T. William Wells wrote: > > Kernel messages should come from the kernel. If users could > > generate them, this could cause many problems. > > How can a user generate a kernel message? If I do a > "logger -p kern.crit blah" this is logged as user.crit even if > the code in question is commented out... If you check out the syslog() code itself, you'll note that it does this translation; logger calls syslog(). But syslog() is an ordinary C function; there is nothing to keep an application from generating "kernel" messages if they don't use syslog() itself but instead generate the messages themselves. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message