Re: patch: make syslog stop spamming any root it finds...
On Sat, Apr 06, 2002 at 08:39:51AM +0200, [EMAIL PROTECTED] wrote: I have always hated the three lines in /etc/syslog.conf which spams root with far too many and far too irrellevant syslog messages, in some cases even with several copies of them. Amen to that. You got my vote. Usually when I set up a FreeBSD box, it's the first thing I turn off. I say commit it. Likewise, it's the first thing I turn off, as well as the *.emerg line that broadcasts to all users. Same here. First things removed on a fresh FreeBSD install. Please commit. Not only the first thing I do with a new FreeBSD box, the first thing I did on FreeBSD: remove those 3 lines from syslog.conf that tell you how many people are poping their mail etc. // George -- GEORGE GEORGALIS, System Admin/Architectcell: 347-451-8229 Security Services, Web, Mail,mailto:[EMAIL PROTECTED] File, Print, DB and DNS Servers. http://www.galis.org/george To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: patch: make syslog stop spamming any root it finds...
I have always hated the three lines in /etc/syslog.conf which spams root with far too many and far too irrellevant syslog messages, in some cases even with several copies of them. Amen to that. You got my vote. Usually when I set up a FreeBSD box, it's the first thing I turn off. I say commit it. Likewise, it's the first thing I turn off, as well as the *.emerg line that broadcasts to all users. Same here. First things removed on a fresh FreeBSD install. Please commit. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: patch: make syslog stop spamming any root it finds...
* Poul-Henning Kamp ([EMAIL PROTECTED]) wrote: I have always hated the three lines in /etc/syslog.conf which spams root with far too many and far too irrellevant syslog messages, in some cases even with several copies of them. Amen to that. You got my vote. Usually when I set up a FreeBSD box, it's the first thing I turn off. I say commit it. (although it's not really a hard job turning it off after an install, but hey, I'm lazy :-) Cheers, Emiel -- Every journalist has a novel in him, which is an excellent place for it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: patch: make syslog stop spamming any root it finds...
Emiel Kollof wrote: * Poul-Henning Kamp ([EMAIL PROTECTED]) wrote: I have always hated the three lines in /etc/syslog.conf which spams root with far too many and far too irrellevant syslog messages, in some cases even with several copies of them. Amen to that. You got my vote. Usually when I set up a FreeBSD box, it's the first thing I turn off. I say commit it. Likewise, it's the first thing I turn off, as well as the *.emerg line that broadcasts to all users. Note however that having syslogd whine to root logins is kind of a discouragement to actually log in as root, and rather have people log in and 'su' instead. But even then, it's I would rather see it dead. :-) Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: patch: make syslog stop spamming any root it finds...
At 11:27 PM +0200 4/5/02, Poul-Henning Kamp wrote: For the life of me I cannot understand why we feel the need to whine like that at any root which crosses our way, so unless somebody can explain to me why this is vital, I'll commit the following patch. There are times when it has been useful to me to have the messages show up immediately on a root-login window, instead of at some later time when I happen to read /var/log/messages. Of course, there are other times when it absolutely infuriates me when some dumb message pops up in the middle of what I'm doing -- particularly if it's a message triggered by something I'm testing. As to your patch, how about leaving the line for *.alert there, but commented out. That would just leave it as an example to show how syslog messages can go to a logged-in user. But when I saw the subject for this thread, I admit I was hoping you meant something different. Is there any good way we could say send to a root login on ttyv0, but NOT to root logged onto any other device? That way, when I wouldn't mind syslog spamming me, I could login to the first virtual terminal, and when I didn't want it I could log into any of the other ones. I guess I'm asking for a new action type, something like: *.alert root@/dev/ttyv0 or maybe just *.alert root@ttyv0 -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message