From owner-freebsd-questions@FreeBSD.ORG Mon Sep 1 12:43:56 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7177E1065682 for ; Mon, 1 Sep 2008 12:43:56 +0000 (UTC) (envelope-from jalmberg@identry.com) Received: from mx1.identry.com (on.identry.com [66.111.0.194]) by mx1.freebsd.org (Postfix) with ESMTP id 08EB08FC58 for ; Mon, 1 Sep 2008 12:43:55 +0000 (UTC) (envelope-from jalmberg@identry.com) Received: (qmail 57669 invoked by uid 89); 1 Sep 2008 12:43:54 -0000 Received: from unknown (HELO ?192.168.1.110?) (jalmberg@75.127.142.66) by mx1.identry.com with ESMTPA; 1 Sep 2008 12:43:54 -0000 In-Reply-To: <48B9FD43.1070508@magidesign.com> References: <2E311D07-5DC9-43FF-9EEF-C56B620A632B@identry.com> <48B9FD43.1070508@magidesign.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3761D93C-F42B-48AC-9295-DFE0E11527DE@identry.com> Content-Transfer-Encoding: 7bit From: John Almberg Date: Mon, 1 Sep 2008 08:43:49 -0400 To: Payne X-Mailer: Apple Mail (2.752.3) Cc: freebsd-questions@freebsd.org Subject: Re: Why the extra shells? 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: Mon, 01 Sep 2008 12:43:56 -0000 > I have seen that when a script is running and it uses the bash shell. This is my main concern at the moment... I am wondering if I killed off an essential process when I killed off those shells... It doesn't seem like it, because everything seems to be working. I'd love to restart the server to see if they come back to life, but that would ruin my uptime stat. As a newbie admin, I take great pride in my 152 day, 100% uptime stat. (Hey, it's the little things in life that make me happy... it obviously isn't the money :-) > I have see that too where you close a ssh session too soon like you > stated. > I'm guessing this is the real cause... I'll be more careful in the future. Thanks: John