grcond error logging

[Steve Dempsey]

IRIS models:	4D/25TG and 4D/340VGX
OS version:	3.3.1

Grcond (the mysterious, undocumented graphics console daemon) displays some
very annoying behavior with regards to its use of SYSLOG.

Every time the news_server is killed by a logout and grcond restarts,
it dumps many lines of copyright legalese into /usr/adm/SYSLOG.
If any system errors then occur, such as recoverable tape errors, the
legalese dissppears and is replaced by all of the errors that have occured
since the last reboot.

The result is the /usr/adm/SYSLOG becomes bloated with repeated listings of
old errors, making it difficult to notice any new ones.  How do I prevent this?
Does grcond use a specific syslogd message type that I can redirect to
/dev/null in /etc/syslog.conf?
---------------------------------------------------------------------------
Steve Dempsey					voice:	  (619) 534-0208
Dept. of Chemistry Computer Facility, 0314	UUCP:	  ucsd!sdempsey
University of Calif. at San Diego		BITNET:	  sdempsey at ucsd
9500 Gilman Drive				INTERNET: sdempsey at ucsd.edu
La Jolla, CA 92093-0314				fax:	  (619) 534-0058