X-Spam-Check-By: sourceware.org
Message-ID: <3820.130.240.136.130.1153173646.squirrel@pinus.tt.luth.se>
Date: Tue, 18 Jul 2006 00:00:46 +0200 (CEST)
Subject: Possible bug in pgrep (procps)
From: "Bengt-Arne Fjellner" <Bengt-Arne DOT Fjellner AT ltu DOT se>
To: cygwin AT cygwin DOT com
User-Agent: SquirrelMail/1.4.5
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


pgrep from procps-3.2.6-1 when asking for an exact match with arguments seems to
demand an extra space after the argument.
See the following sequence.

No space after the f on the commandline
$ emacs f&
[1] 2072

without extra space
$ pgrep  -x -f "emacs f"

with extra space after f
$ pgrep  -x -f "emacs f "
2072

Bug or my misunderstanding ?


-- 
Bengt-Arne Fjellner




--
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/