Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!husc6!rice!sun-spots-request
From: pdn!larry@uunet.uu.net (Larry Swift)
Newsgroups: comp.sys.sun
Subject: Re: syslogd
Message-ID: <5198@pdn.UUCP>
Date: 30 Dec 88 18:41:55 GMT
References: <8812130004.AA26573@uunet.UU.NET>
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 11
Approved: Sun-Spots@rice.edu
Original-Date: 21 Dec 88 12:59:51 GMT
X-Sun-Spots-Digest: Volume 7, Issue 82, message 5 of 18

munnari!anu.anu.oz.au!mbl900@uunet.uu.net (Mathew B Lim) writes:
>above fix has not been done). Oh yes, after editing /etc/syslog.conf, you
>should kill syslogd and restart it.

Just do a "kill -1  `cat /etc/syslog.pid`".  The syslogd daemon will
re-scan the syslog.conf without losing messages.

Larry Swift                     UUCP: {peora,uunet}!pdn!larry
Paradyne Corp., LG-129          Phone: (813) 530-8605
P. O. Box 2826
Largo, FL, 34649-9981