public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Herb Maeder <maeder-cygml@maeder.org>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: OpenSSH-5.1p1-6 (-7)
Date: Sat, 08 Nov 2008 15:12:00 -0000	[thread overview]
Message-ID: <8968.1226157135@maeder.org> (raw)
In-Reply-To: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com> 's message of                  Fri, 07 Nov 2008 17:10:02 EST.

On 07 Nov 2008 17:10:02 EST, Christopher Faylor wrote:
> 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.

Yes, that makes sense.  Zero or one was probably the intent.  Thanks for
pointing it out.

Though the trailing $ probably still makes sense to restrict it to
matching only ssh or sshd processes.  grep -qP '/sshd?$'

Herb.

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

  parent reply	other threads:[~2008-11-08 15:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cgf-use-the-mailinglist-please@cygwin.com>
2008-10-05 17:54 ` cygcheck output sometimes gets truncated when piped (cygwin-1.7) Herb Maeder
2008-10-18  0:38 ` cygwin-1.7 sshd/ssh-host-config install issues on Vista Herb Maeder
     [not found] ` <0MKpdM-1KqzqB1Dn6-0009Uj@mx.kundenserver.de>
2008-10-20 11:28   ` Corinna Vinschen
2008-10-28 20:42 ` Apologies for multiple messages (Please Help!) Herb Maeder
2008-11-08 15:12 ` Herb Maeder [this message]
2008-11-20 10:13 ` rsync 3.0.4 over ssh hanging on cygwin 1.7 Herb Maeder
2008-11-20 18:53   ` Fred Kemp
2008-11-20 23:38     ` Brett Serkez
     [not found] <corinna-cygwin@cygwin.com>
2008-11-07 17:52 ` [ANNOUNCEMENT] Updated: OpenSSH-5.1p1-6 (-7) Herb Maeder
2008-11-07 18:36   ` Christopher Faylor
2008-11-07 21:17 ` Herb Maeder
2008-11-07 21:38 ` Herb Maeder
2008-11-07 22:10   ` Christopher Faylor
2008-11-07 11:04 Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8968.1226157135@maeder.org \
    --to=maeder-cygml@maeder.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).