Mail Archives: cygwin/2001/02/05/10:05:09
Corinna,
Thanks for responding. However, I've setup sshd
to run as a service under the system account so
that I can log in via password mechanism under
different accounts, but a system account PID
cannot be easily killed by a regular account,
even if the regular account belongs to the administrative
group.
I may just have to run it under
a regular account and login as that account,
or an account that's been bumped up as per your
doc, either of which leaves sshd running
as a non-service process -- at least while
testing.
(I didn't have a script to pull out the pid,
but have tried repeatedly to 'kill #' after
ps -aef manually)
Heitzso
-----Original Message-----
From: Corinna Vinschen [mailto:cygwin AT cygwin DOT com]
Sent: Friday, February 02, 2001 4:49 PM
To: cygwin AT cygwin DOT com
Subject: Re: sshd and stack dump problem
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
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -