From owner-freebsd-questions@FreeBSD.ORG Sun Jan 20 18:35:37 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 F1F3716A419 for ; Sun, 20 Jan 2008 18:35:37 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id C045513C45A for ; Sun, 20 Jan 2008 18:35:37 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.2/8.14.2) with ESMTP id m0KIZPVt008187; Sun, 20 Jan 2008 11:35:25 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.2/8.14.2/Submit) with ESMTP id m0KIZPrt008184; Sun, 20 Jan 2008 11:35:25 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 20 Jan 2008 11:35:25 -0700 (MST) From: Warren Block To: Jonathan Horne In-Reply-To: <200801200947.13279.freebsd08@dfwlp.com> Message-ID: <20080120113049.Y8014@wonkity.com> References: <200801200947.13279.freebsd08@dfwlp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (wonkity.com [127.0.0.1]); Sun, 20 Jan 2008 11:35:25 -0700 (MST) Cc: freebsd-questions@freebsd.org Subject: Re: check processes started by inetd 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, 20 Jan 2008 18:35:38 -0000 On Sun, 20 Jan 2008, Jonathan Horne wrote: > how can i check to see the processes that have been started by inetd? i mean > other than reading the inetd.conf file... but something like top or something > that shows me the processes that are actually running? Kind of depends on what you're looking for, but ps ax, or enable inetd logging, or maybe sockstat. If you're new to FreeBSD, remember that inetd isn't enabled by default, and a lot of the daemons it's used to start on other systems can be run on their own. -Warren Block * Rapid City, South Dakota USA