X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <31b7d2790801172004s5720b8c4ucf0e78162298a189@mail.gmail.com> Date: Thu, 17 Jan 2008 22:04:22 -0600 From: "DePriest, Jason R." To: cygwin AT cygwin DOT com Subject: Re: ps executable does not appear to match source In-Reply-To: <4a89b8680801171938t50c143acia8ac71019bd75999@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4a89b8680801171938t50c143acia8ac71019bd75999 AT mail DOT gmail DOT com> X-IsSubscribed: yes 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 Jan 17, 2008 9:38 PM, <> wrote: > The ps that comes with Cygwin is missing a number of features that > appear to be in the procps-3.2.7/ps/ source code. The source code > does not look like it was used to build the executable. Is this > correct? Cygwin has both ps and procps available. The ps in Cygwin has the advantage of showing Windows processes, too. The procps is just what you'd expect. -Jason -- NOTICE: Reading this email message requires root privileges which you do not appear to possess. Sorry, dude. -- 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/