Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!kodak!ispd-newsserver!garden.ssd.kodak.com!weimer
From: weimer@garden.ssd.kodak.com (Gary Weimer (253-7796))
Newsgroups: comp.unix.questions
Subject: Re: Error messages to the console
Message-ID: <1991May17.172529.28248@ssd.kodak.com>
Date: 17 May 91 17:25:29 GMT
References: <26918@adm.brl.mil>
Sender: news@ssd.kodak.com
Reply-To: weimer@ssd.kodak.com
Organization: Eastman Kodak Co.; Rochester, NY
Lines: 16


In article <26918@adm.brl.mil>, gautier@charly.taclog.af.mil (Sgt
Richard Gautier) writes:
|> For standard error messages of the OOOPS, I messed up
|> variety, I would depend on just writing the output to
|> stderr with a fprintf(stderr,"OOPS");
|> 
|>   However, if you must write to the console, you can
|> open /dev/console on most Unix boxes, and fprintf your
|> info to that.  On some Unix boxes, there is an errorlog
|> that is constantly checked and sent to the console (used
|> for DISK crashes, etc.)  Do a ps and see if you have any
|> cat -u processes running for console.

Isn't syslog(3) the "standard" way? I don't have access to many Unix
varieties, so I don't know...