From owner-freebsd-questions@FreeBSD.ORG Sun Apr 23 13:49:33 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5474316A409 for ; Sun, 23 Apr 2006 13:49:33 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABCAE43D49 for ; Sun, 23 Apr 2006 13:49:32 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from localhost (monrovll-cuda1-24-53-251-44.pittpa.adelphia.net [24.53.251.44]) (AUTH: LOGIN wmoran, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Sun, 23 Apr 2006 09:49:31 -0400 id 00056414.444B85EB.0000C94F Date: Sun, 23 Apr 2006 09:49:28 -0400 From: Bill Moran To: perikillo Message-Id: <20060423094928.2db21ce3.wmoran@collaborativefusion.com> In-Reply-To: <51d7a5160604230303o514d2cabn90179490fc5698f@mail.gmail.com> References: <51d7a5160604230303o514d2cabn90179490fc5698f@mail.gmail.com> Organization: Collaborative Fusion X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: bacula daemon dosent died..? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Apr 2006 13:49:33 -0000 perikillo wrote: > Hi people, iam testing bacula 1.38.8, the problem i have right now > is that if i want to stop the daemon: > > zorra#/usr/local/etc/rc.d/bacula-dir.sh stop > Stopping bacula-dir. > Waiting for PIDS: 910, 910, > 910,910,910,910,910,910,910,910,910,910,910,910,910,910,910, 910, 910, > 910,910,910,910,910,910,910,910,910,910,910,910,910,910,910, > 910,910,910,910,910, 910, > 910,910,910,910,910,910,910,910,910,910,910,910,910,910,910, > 910,910,910,910, > 910, 910, 910,910,910,910,910,910,910,910,910,910,910,910,910,910,910, > 910,910,910,910, 910, 910, > 910,910,910,910,910,910,910,910,910,910,910,910,910,910,910, > 910,910,910,910, > 910, 910, 910,910,910,910,910,910,910,910,910,910,910,910,910,910,910, > 910,910,910,910,910, 910, > 910,910,910,910,910,910,910,910,910,910,910,910,910,910,910, > 910,910,910,910, > > top say: > > idle 0.0% 21.9% user 0.0% nice 79.0 system > > I need to use the kill command to stop the daemon, has someone any > idea about how to resolve this problem...? What's the daemon doing when you try to stop it? From the high system time, it looks like it's in the process of running a job. I doubt it's going to shut down until the job completes, which is the behaviour I would expect. -- Bill Moran Potential Technologies http://www.potentialtech.com