From owner-freebsd-questions Thu Mar 30 5:57:37 2000 Delivered-To: freebsd-questions@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id D8B6C37B658 for ; Thu, 30 Mar 2000 05:57:31 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12afRf-0006kE-00; Thu, 30 Mar 2000 15:57:11 +0200 From: Sheldon Hearn To: Micke Josefsson Cc: =?Windows-1252?Q?Ari_Sigur=F0sson?= , freebsd-questions@FreeBSD.ORG Subject: Re: messages on screen In-reply-to: Your message of "Thu, 30 Mar 2000 15:34:07 +0200." Date: Thu, 30 Mar 2000 15:57:11 +0200 Message-ID: <25929.954424631@axl.ops.uunet.co.za> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Mar 2000 15:34:07 +0200, Micke Josefsson wrote: > kill -HUP 1164 > > Kills process number 1164 (PID=Process ID). Use top or 'ps -ax' to list > processes. Actually, most deamons leave a "pid file" in /var/run to assist you with this. In the case of syslogd, you can usually do this: kill -HUP `cat /var/run/syslog.pid` Note that it's syslod.pid and _not_ syslogd.pid. FreeBSD also has a killall(1) utility which kills (possibly multiple) processes by name. You could do this: killall -HUP syslogd However, killall(1) does not exist on all platforms and this "lazy" way of doing things can cause some serious problems if you happen to catch forking daemons at the wrong moment. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message