From owner-freebsd-current  Sat Nov 22 01:18:24 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA25157
          for current-outgoing; Sat, 22 Nov 1997 01:18:24 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from shasta.wstein.com (joes@shasta.wstein.com [207.173.11.132])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA25152
          for <freebsd-current@freebsd.org>; Sat, 22 Nov 1997 01:18:20 -0800 (PST)
          (envelope-from joes@shasta.wstein.com)
Received: (from joes@localhost)
	by shasta.wstein.com (8.8.8/8.8.8) id BAA06933;
	Sat, 22 Nov 1997 01:18:01 -0800 (PST)
From: Joseph Stein <joes@seaport.net>
Message-Id: <199711220918.BAA06933@shasta.wstein.com>
Subject: Re: Way to know if someone fingers you
In-Reply-To: <Pine.BSF.3.96.971121133711.1742A-100000@logues.rhn.orst.edu> from logue at "Nov 21, 97 01:42:54 pm"
To: logue@logues.rhn.orst.edu (logue)
Date: Sat, 22 Nov 1997 01:18:01 -0800 (PST)
Cc: chris@c-unix.mountain.net, freebsd-current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> goes are something that I have yet to learn as well.  In fact, I would
> like to know every possible way something can write to syslog so that I
> can solve this problem once and for all.  For example, I want to route
> tcpd (tcp_wrapper) messages to /var/log/secure...

To find out "every possible way something can write to syslog",

man 8 syslogd 

To find out how to filter it out, 

man 5 syslog.conf

To find out which program uses which facilities (and how to filter it)

UTSL (Use the source, Luke)


joe