Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!ipso!runxtsa!bde From: bde@runx.oz.au (Bruce Evans) Subject: Re: Rotating the syslogs Message-ID: <1993Mar30.224405.18613@runx.oz.au> Organization: RUNX Un*x Timeshare. Sydney, Australia. References: <1p77tt$rq3@usenet.INS.CWRU.Edu> <g89r4222.733427031@kudu> Date: Tue, 30 Mar 93 22:44:05 GMT Lines: 20 In <1p77tt$rq3@usenet.INS.CWRU.Edu> david@jake.EEAP.CWRU.Edu (David Nerenberg) writes: >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. kill -9 works OK here. kill -TERM is better. I haven't used cron much under 386BSD and usually empty the messages file using ">/var/log/messages". syslogd doesn't have to be killed. The next write goes to the front of the file because syslogd opens the file in append mode. -- Bruce Evans bde@runx.oz.au