Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!usenet.ins.cwru.edu!jake.EEAP.CWRU.Edu!david
From: david@jake.EEAP.CWRU.Edu (David Nerenberg)
Newsgroups: comp.os.386bsd.questions
Subject: Rotating the syslogs
Date: 29 Mar 1993 16:25:33 GMT
Organization: Case Western Reserve University
Lines: 21
Distribution: world
Message-ID: <1p77tt$rq3@usenet.INS.CWRU.Edu>
NNTP-Posting-Host: jake.eeap.cwru.edu
I am trying to rotate my syslogs from cron. The cron side of things
is fine. Fir example, I move messages to messages.OLD and touch a
new messages file. On a normal machine, I would do something like this
to tell sysleg to use the new file: kill -HUP `cat /var/run/syslog.pid`
and all would be well. However, on 386bsd, this does nothing. I can
not get syslogd to use the new file without re-booting. So, I went
for drastic measures and kill -9'ed syslogd thinking that I would then
just re-start it. But, that causes the machine to crash! I love it,
a syslog dependancy in the OS.
Does anyone have any ideas on how I might fix this before I throw this
machine out the window? I can't even think of a way to debug this since
either the OS or syslog seems broken, and I can't debug one without the
other.
-Dave
--
david@elwood.eeap.cwru.edu David Nerenberg
73107,177 CompuServe Electrical Engineering & Applied Physics
NY: H-516-751-6344 Case Western Reserve University
W-516-751-8111 W-216-368-2982 H-216-754-2085