recently, this Q&A was posted to this list:
(excerpt)
I erased (simply by writing rm binary.errlog) in our Digital AlphaServer running
Digital Unix 4.0b due to the huge file size (about 60 MB). And all the messages
giving in about CAM (SCSI) events and this message repeated every 5 minutes and
logged in binary.errlog.
But after this procedure it seems that system does not re-generate
binary.errlog. Is that expectable.? or should I re-run some daemon to regenerate
this file??
SOLUTION:
1. touch /var/adm/binary.errlog
2. kill -HUP 'cat /var/run/binlog.d.pid'
my question is this:
is there something similar for syslog.dated? it seems that the entries from
syslogd have been running rampant lately, using major disk space. i have
searched the slim documentation available to me, none the wiser.
if anyone has ANY (even if it is small) information on this problem or the
process in general, i would welcome it.
i will summarize
thank you
josie
*****************************************************************************
Josie Young young_at_nuc006.psc.sc.edu
Unix Sys Admin (803) 777 5753
Nuclear Grp
Dept Physics & Astronomy
Univ of SCarolina
Received on Fri Oct 17 1997 - 22:42:03 NZDT