X-Spam-Check-By: sourceware.org Message-ID: X-Sender: vilarneto AT hotmail DOT com In-Reply-To: <028401c68384$ea579d50$a501a8c0@CAM.ARTIMI.COM> From: "Vilar Camara" To: cygwin AT cygwin DOT com Subject: RE: sshd+ssh localhost connects, but don't reach the shell Date: Tue, 30 May 2006 01:26:22 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > >> That's right, I had looked at it and completely forgot to mention it. > >> But my Event Log doesn't add anyting to our discussion: there are only > >> log entries saying: > >> `sshd' service started > >> `sshd' service stopped, exit status: 0 > >> `sshd' service stopped, exit status: 255 > >> sshd: PID XXXX: Server listening on 0.0.0.0 port 22 > >> sshd: PID XXXX: Received signal 15; terminating > > > > So it looks normal, as if everything is working fine. > > Eh? Isn't signal 15 a SEGV? SIGTERM, perhaps? The event happens when I gracefully stop the service via "cygrunsrv -E sshd". It appears together with event "`sshd' service stopped, exit status: 255". -- Regards, Vilar Camara Neto -- 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/