From owner-freebsd-questions@FreeBSD.ORG Fri Feb 2 01:08:49 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C58316A400 for ; Fri, 2 Feb 2007 01:08:49 +0000 (UTC) (envelope-from spamtrap@liv.ic.unicamp.br) Received: from turing.liv.ic.unicamp.br (liv-gw.ic.unicamp.br [143.106.7.169]) by mx1.freebsd.org (Postfix) with ESMTP id B429113C481 for ; Fri, 2 Feb 2007 01:08:48 +0000 (UTC) (envelope-from spamtrap@liv.ic.unicamp.br) Received: by turing.liv.ic.unicamp.br (Postfix, from userid 551) id 7CBEB110272; Thu, 1 Feb 2007 22:42:46 -0200 (BRDT) Received: from turing (turing [10.0.0.1]) by turing.liv.ic.unicamp.br (Postfix) with ESMTP id 3A4A0110190; Thu, 1 Feb 2007 22:42:45 -0200 (BRDT) Date: Thu, 1 Feb 2007 22:42:45 -0200 (BRDT) From: "Felipe Bergo (lists)" X-X-Sender: spamtrap@turing To: Andrew Falanga In-Reply-To: <340a29540702011007mcdb45bcya1db8732d78ecd34@mail.gmail.com> Message-ID: References: <340a29540702011007mcdb45bcya1db8732d78ecd34@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Checker-Version: SpamAssassin 3.0.6 (2005-12-07) on turing.liv.ic.unicamp.br X-Spam-Level: X-Spam-Status: No, score=-4.6 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.6 Cc: freebsd-questions Subject: Re: ps oddity 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: Fri, 02 Feb 2007 01:08:49 -0000 > Now, here's the strange part. When running under my user id, even in daemon > mode, ps -aux | grep would show me the daemon process. However, now > that it's running as root, it doesn't. Why is that? The only way I've been > able to tell that it's running is by using sockstat. Are you doing ps -aux | grep root instead of ps -aux | grep previous_user_who_is_not_running_the_process ? Look for your process in ps -aux | less Still missing ? -- Felipe