Date: Fri, 7 Nov 2008 17:10:02 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: OpenSSH-5.1p1-6 (-7)
Message-ID: <20081107221002.GA31853@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <corinna-cygwin@cygwin.com> <94965.1226093864@maeder.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <94965.1226093864@maeder.org>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Fri, Nov 07, 2008 at 01:37:44PM -0800, Herb Maeder wrote:
>On 07 Nov 2008 12:00:56 +0100, Corinna Vinschen wrote:   
>> This is a bugfix release which fixes a bug in the ssh-host-config script
>> which stumbles over user names with a substring of "ssh" in them and
>> thinks that ssh processes are still running.
>
>Is the intent now to catch only processes named 'sshd'?  If so, the
>current "grep -q 'sshd*$'" may still be a little too loose.  For example, 
>it could match stuff like "/home/user/flosshdd".  Ok, maybe not likely, 
>but still it would cause the script to end in an error.
>
>Assuming we can depend on "ps -ef" always printing full path names without 
>any arguments, then "grep -q '/sshd$'" might do the trick.  Is there any
>reason to catch multiple trailing d's?

It's possible that Corinna was looking for zero or more d's.

So, something like grep -qP '/sshd?' would accommodate that.

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/