Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!ames!enews.sgi.com!news.sgi.com!howland.erols.net!rill.news.pipex.net!pipex!newsfeed.internetmci.com!news.easystreet.com!not-for-mail From: "Ted Mittelstaedt" <tedm@portsoft.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Need More Answers ... Look here ! Date: 20 Mar 1997 21:05:32 GMT Organization: Portland Software Lines: 25 Message-ID: <01bc3572$b1a29f60$7c01a8c0@teds.portsoft.com> References: <01bc34ab$b59c42a0$664c1bcc@tony.gcr1.com> NNTP-Posting-Host: sunnet.portsoft.com X-Newsreader: Microsoft Internet News 4.70.1155 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37535 Tony <tony@gcr1.com> wrote in article <01bc34ab$b59c42a0$664c1bcc@tony.gcr1.com>... > Here are a few thing I'm still trying to find out ... > > Can you direct the console to a telnet session ..? not just login and look > around .. > I'd like to be able to see daemons coming up and shutting down .. and see > error > messages that only show up at the console ... > look at the manual pages for syslogd, and syslog.conf to see how to redirect error messages to another machine, or e-mail. The only error messages I know of that cannot be redirected this way are major error faults, such as panics, broken network cables, lost interrupts, scsi adapter failures and so on and you'd better danm well be at the console when these happen because you aren't going to be able to do squat if your not.