From owner-freebsd-security Tue May 7 7: 8:49 2002 Delivered-To: freebsd-security@freebsd.org Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by hub.freebsd.org (Postfix) with ESMTP id 5D2B137B412 for ; Tue, 7 May 2002 07:08:35 -0700 (PDT) Received: from dc.cis.okstate.edu (localhost [127.0.0.1]) by dc.cis.okstate.edu (8.11.6/8.11.3) with ESMTP id g47E8Vl29936 for ; Tue, 7 May 2002 09:08:34 -0500 (CDT) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200205071408.g47E8Vl29936@dc.cis.okstate.edu> To: freebsd-security@FreeBSD.ORG Subject: I am My Own Worst Enemy Regarding Denial of Service! Date: Tue, 07 May 2002 09:08:31 -0500 From: Martin McCormick Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I set up our syslog.conf on a FreeBSD system to notify all of us when the network equipment we monitor sends a critical syslog message. This works perfectly and we get the messages on all logged-in TTY's. The system breaks down if one of our pieces of gear goes in to a failure mode in which it sends a continuous or more or less continuous stream of messages to everybody with such frequency that the window or screen is quickly filled. Is there any way to define a login in such a way as to escape the bombardment? The idea is to define one terminal with no messages in order to be able to work without interruption on the system in question. Martin McCormick WB5AGZ Stillwater, OK OSU Center for Computing and Information Services Network Operations Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message