Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 31 Jul 2001 10:43:08 -0400 (EDT)
From: Prentis Brooks <prentis AT aol DOT net>
To: <cygwin AT cygwin DOT com>
Subject: "Illegal User" logging into sshd
Message-ID: <Pine.GSO.4.33.0107311040200.26124-100000@magetower.office.aol.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Ok, I finally pinpointed the problem, but I don't like my solution.

Basically, it appears that sshd is not recognizing any changes to /etc/passwd
since it started.  To solve this I had to connect to the host and stop all
instances of sshd then restart clean, not pretty and not viable if I want to
script changes to the passwd files across a farm.  Is there another way to
get sshd to review the files, will it accept a kill -HUP and if so, how can
I send the hup, since I can't get the pid from within an ssh session (or is
there a way I haven't found yet?)


Prentis Brooks	| prentis AT aol DOT net | 703-265-0914 | AIM: PrentisB
System Administrator - Web Infrastructure & Security

       A knight is sworn to valor.  His heart knows only virtue.  His blade
       defends the helpless.  His word speaks only truth.  His wrath undoes the
       wicked. - the old code of Bowen, last of the dragonslayers


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/