Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 31 Jul 2001 17:16:55 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: "Illegal User" logging into sshd Message-ID: <20010731171655.I490@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.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 prentis@aol.net on Tue, Jul 31, 2001 at 10:43:08AM -0400 On Tue, Jul 31, 2001 at 10:43:08AM -0400, Prentis Brooks wrote: > 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?) The correct solution would be a patch to the Cygwin DLL itself to check the file modification date of /etc/passwd and /etc/group and reload them when appropriate. A patch would be really welcome. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/