X-Spam-Check-By: sourceware.org Date: Tue, 1 May 2007 09:36:03 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: display ps command line parameters Message-ID: <20070501133603.GA17841@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4edba06c76Andy AT jet-net DOT co DOT uk> <4edc19cdd3Andy AT jet-net DOT co DOT uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4edc19cdd3Andy@jet-net.co.uk> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Tue, May 01, 2007 at 10:41:19AM +0100, Andy AT Jet-Net wrote: >> An alternative would be to parse /proc/PID/cmdline. >I think I'll use Tony's solution, as I don't have pstree available on my >"development" or "live" Cygwin installation. This would be quicker as I can >use it straight "out of the box". > >I was looking for exactly something like the cmdline file yesterday! It seems rather silly to parse /proc/PID/cmdline when you could just use procps. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/