From owner-freebsd-hackers Wed Apr 12 08:16:59 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA15644 for hackers-outgoing; Wed, 12 Apr 1995 08:16:59 -0700 Received: from fslg8.fsl.noaa.gov (fslg8.fsl.noaa.gov [137.75.131.171]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA15638 for ; Wed, 12 Apr 1995 08:16:57 -0700 Received: by fslg8.fsl.noaa.gov (5.57/Ultrix3.0-C) id AA16522; Wed, 12 Apr 95 15:16:54 GMT Received: by junco.fsl.noaa.gov (1.38.193.4/SMI-4.1 (1.38.193.4)) id AA21967; Wed, 12 Apr 1995 09:16:54 -0600 Date: Wed, 12 Apr 1995 09:16:54 -0600 From: kelly@fsl.noaa.gov (Sean Kelly) Message-Id: <9504121516.AA21967@junco.fsl.noaa.gov> To: bertus@mikom.csir.co.za Cc: hackers@FreeBSD.org In-Reply-To: <199504121158.NAA26689@zibbi.mikom.csir.co.za> (message from Bertus Pretorius on Wed, 12 Apr 1995 13:58:11 +0200 (SAT)) Subject: Re: syslog to printer Sender: hackers-owner@FreeBSD.org Precedence: bulk >>>>> "Bertus" == Bertus Pretorius writes: Bertus> Hi, i'm looking for something or someway whereby the Bertus> syslog could be directed to a printer rather than to a Bertus> file. Although not as attractive, here's a hardware solution: use a serial port as the console and attach a printing terminal; or a Wyse or other terminal that can log all I/O through to a printer. I set up such an installation at one site and it proved to be quite effective to find out what was going wrong at odd hours. --k