From owner-freebsd-questions Sat Feb 1 16:31:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA19200 for questions-outgoing; Sat, 1 Feb 1997 16:31:01 -0800 (PST) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA19190 for ; Sat, 1 Feb 1997 16:30:58 -0800 (PST) Received: (from dubois@localhost) by night.primate.wisc.edu (8.8.4/8.8.2) id SAA28611; Sat, 1 Feb 1997 18:30:50 -0600 (CST) Message-ID: Date: Sat, 1 Feb 1997 18:30:50 -0600 From: dubois@primate.wisc.edu (Paul DuBois) To: tlayton@global-sol.com Cc: questions@freebsd.org Subject: Re: start & stop syslogd ? References: <199702011919.TAA26175@mail.global-sol.com> X-Mailer: Mutt 0.58.1 Mime-Version: 1.0 In-Reply-To: <199702011919.TAA26175@mail.global-sol.com>; from Timothy P. Layton, Sr. on Feb 1, 1997 17:37:08 +0000 Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Timothy P. Layton, Sr. writes: > Is there a "best"or most correct way to stop and re-start the > syslogd process ? > > I don't know if it is correct to just kill it and restart it by > executing /usr/sbin/syslogd. That should probably work, although you can probably accomplish your goal less intrusively by sending syslogd a HUP (hangup) signal. See man syslogd. -- Paul DuBois dubois@primate.wisc.edu Home page: http://www.primate.wisc.edu/people/dubois Software: http://www.primate.wisc.edu/software