Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!spool.mu.edu!sol.ctr.columbia.edu!startide.ctr.columbia.edu!wpaul
From: wpaul@ctr.columbia.edu (Bill Paul)
Newsgroups: comp.os.386bsd.questions
Subject: Re: changing 2.0 behavior
Date: 4 Dec 1994 19:17:10 GMT
Organization: Columbia University Center for Telecommunications Research
Lines: 49
Message-ID: <3bt4jm$q9@sol.ctr.columbia.edu>
References: <D05wFw.v2@murdoch.acc.Virginia.EDU> <3bmetj$6be@sol.ctr.columbia.edu> <D0AC36.FLE@jester.GUN.de>
NNTP-Posting-Host: startide.ctr.columbia.edu
X-Newsreader: TIN [version 1.2 PL2]
Daring to challenge the will of the almighty Leviam00se, Michael Gerhards
(michael@jester.GUN.de) had the courage to say:
: In article <3bmetj$6be@sol.ctr.columbia.edu> , Bill Paul wrote:
: > : First off, I get messages on the consoles (ttyv{0,1,2}) every time
: > : ANYONE logs in. I'm used to seeing messages on every terminal when
: > : root logs in.
: [..]
: > : Anyways, > : how do I stop these?
: [..]
: > a) Get the source code.
: [..]
: Recompile login to stop these messages ? I think it is enough to change
: the file /etc/syslog.conf. Change the lines:
: *.err;kern.debug;auth.notice;mail.crit /dev/console
: *.notice;auth.debug root
: Remove the auth-statement and the messages will go away. Or did I get
: something totally wrong here ?
: Michael
: --
Uhm... close, I think, but not quite. Changing it rather than removing it
outright might work better. If login's extra messages are logged at a
different priority than the usual ones (i.e. auth.notice for the 'superflous'
ones and auth.crit for the important ones (failed logins, root logins)),
then changing auth.notice to auth.crit might do the trick. In addition, you
could have the auth.notice messages logged to a special file, which you
could then ignore at your lesiure.
But that would apply to *all* messages logged at auth.notice, not just
the ones generated by login. For some this might be considered overkill.
As far as I'm concerned, it's easier just to make a new login binary.
Altering the system to make up for one program's undesired behavior isn't
the way to go, unless you're running a commercial OS, of course. :)
-Bill
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Bill Paul System Manager
wpaul@ctr.columbia.edu Center for Telecommunications Research
Columbia University, New York City
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Møøse Illuminati: ignore it and be confused, or join it and be confusing!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~