Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 2 Feb 2001 22:49:09 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: sshd and stack dump problem Message-ID: <20010202224909.S19867@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from xxh1@cdc.gov on Fri, Feb 02, 2001 at 12:16:49PM -0500 On Fri, Feb 02, 2001 at 12:16:49PM -0500, Heitzso wrote: > * when I kill the service (sc stop service_name) > the service doesn't die. I'm guessing SRVANY > is stopped but that sshd has spawned itself > out of SRVANY's control and lives on. That's normal behaviour since sshd doesn't have a clue what a NT service is. SRVANY stops but you will have to kill the application by hand. Personally, I'm using the following script to stop sshd: #!/bin/sh net stop sshd >/dev/null 2>&1 PID=`ps -e | awk '/sshd/{print $1}'` if [ -n "${PID}" ] then kill $PID fi Sorry, I have no clue why ls hangs. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple