Date: Tue, 20 May 1997 17:22:22 -0700 (PDT) From: phillip@rmit.edu.au To: freebsd-gnats-submit@FreeBSD.ORG Subject: docs/3645: TCP_wrappers package doesn't mention where logging information goes. Message-ID: <199705210022.RAA06418@hub.freebsd.org> Resent-Message-ID: <199705210030.RAA06827@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 3645 >Category: docs >Synopsis: TCP_wrappers package doesn't mention where logging information goes. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue May 20 17:30:00 PDT 1997 >Last-Modified: >Originator: Phillip Musumeci >Organization: RMIT Computer Systems Eng. Melbourne AUSTRALIA >Release: 2.2.1R >Environment: FreeBSD mirriwinni.cse.rmit.edu.au 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE #0: Mon Apr 7 15:22:40 EST 1997 phillip@mirriwinni.cse.rmit.edu.au:/usr/src/sys/compile/MARINA i386 >Description: If you want to enable logging of connections for TCP wrappers, you need to read the README file in the source distribution *and* the patch file in the ports area to see what class (auth) and priority (probably info) the log messages to syslogd will have. Then you can adjust the /etc/syslog.conf file. Perhaps we should mention this in the message displayed when the tcp_wrappers package is installed and/or include a sample line in the /etc/syslog.conf file. It might also be appropriate to choose a standard log file for messages such as those from tools like tcp_wrappers. A sample syslog.conf line for tcp_wrappers logging is enclosed: auth.info /var/log/tcplog This line was included just beneath the mail.info line in the syslog.conf file. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705210022.RAA06418>