Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!usenet.eel.ufl.edu!gatech!news.mathworks.com!nntp.primenet.com!uucp.primenet.com!news.typo.org!web From: BOFH <web@typo.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Syslogd Output to Printer Date: 17 Jul 1996 21:48:30 GMT Organization: typo.org Lines: 22 Message-ID: <4sjn3e$2gs@typo.org> References: <4sjko5$964@herald.concentric.net> NNTP-Posting-Host: typo.org Damien Thorn <Judasg@cris.com> wrote: : While I'm asking device-related questions, is there an easy way to : configure syslog to dump output to a dot matrix printer rather than : to the console? : More specifically, how do I need to configure a device file for the : printer? Never tried this, but I would bet you can simply specify /dev/lp or some equivilant as the file and get away with it. : Do other people log to hardcopy for a more 'permanent' audit of certain : activities, or am I simply Paranoid? <g>! Um, depends. mostly, they're not needed. How often do events occur in syslog that you need a hard copy of. Best bet is to have a server elsewhere that acts as a central archive for your systems. Make this system inaccessable except from console (eg, kill -9 inetd). Have all the machines on your netwrok log *.* to this one. If you want to archive them, do so by a backup of the log directory once a week or so and store the tapes. Makes them a bit hard to get at but no harder than sifting through miles of fan fold paper.