From owner-freebsd-stable Sun Nov 16 02:48:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA10353 for stable-outgoing; Sun, 16 Nov 1997 02:48:26 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from dev.random.nu (rpc.ypxfrd@iskh122.haninge.kth.se [130.237.83.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA10347 for ; Sun, 16 Nov 1997 02:48:17 -0800 (PST) (envelope-from dev.random@dev.random.nu) From: dev.random@dev.random.nu Received: from localhost (random@localhost) by dev.random.nu (8.8.7/8.8.7) with SMTP id LAA24779 for ; Sun, 16 Nov 1997 11:47:04 +0100 (CET) (envelope-from dev.random@dev.random.nu) Date: Sun, 16 Nov 1997 11:46:57 +0100 (CET) X-Sender: random@dev.random.nu To: freebsd-stable@freebsd.org Subject: logging login.conf limits? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk wouldn't it be optimal if login.conf violations were logged in syslog/console? I see many uses for this (if there is not already a way to do this.. nothing was mentioned in login.conf that I saw). - finding attempted forkbombs. - finding when httpd & sendmail hit their login.conf limits. (which if some magazine reviewers knew about, we would probably been rated better). - violations of the hosts.deny & times.deny (when their implemented?) _________________________________________________________________ thomas stromberg % sysadmin(royal.institute.of.technology@haninge/stockholm) smtp(dev.random@dev.random.nu)%irc(devrandom)%talkd(random@dev.random.nu)