X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 7 Nov 2008 17:10:02 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: OpenSSH-5.1p1-6 (-7) Message-ID: <20081107221002.GA31853@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <94965 DOT 1226093864 AT maeder DOT 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 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 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/