| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-Spam-Check-By: | sourceware.org |
| Date: | Tue, 31 Jul 2012 14:28:24 +0200 |
| From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: sshd crashing |
| Message-ID: | <20120731122824.GA30188@calimero.vinschen.de> |
| Reply-To: | cygwin AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| References: | <CA+7conmf=HORJ9nscNe4CA67EAeO+n7H6GkpVK4cPq315wJtzg AT mail DOT gmail DOT com> <34233493 DOT post AT talk DOT nabble DOT com> |
| MIME-Version: | 1.0 |
| In-Reply-To: | <34233493.post@talk.nabble.com> |
| User-Agent: | Mutt/1.5.21 (2010-09-15) |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Id: | <cygwin.cygwin.com> |
| List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
| Sender: | cygwin-owner AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Jul 30 17:49, Aleš wrote: > > Hello, > > I can confirm the issue. It's occurring after upgrade to 1.7.16 and seems to > be limited to VMWare guests in my case. Any write attempt within the /etc > directory causes sshd to crash. Other directories are fine. > > uname -a before upgrade (sshd doens't crash): > CYGWIN_NT-6.0-WOW64 dbs6 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin > and after upgrade (sshd crashes): > CyGWIN_NT-6.0-WOW64 dbs6 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin > > > cygrunsrv -S sshd > ssh localhost > $ touch /etc/x > Connection to localhost closed by remote host. > Connection to localhost closed. > > > A familiar message appears in the event log: > service sshd failed: signal 11 raised > > The /etc/x file gets created in the example above. If running vim /etc/x > instead, the .x.swp file gets also created and a vim-nox.exe process keeps > on living, taking all CPU resources till it's killed. > > I have reproduced this on over ten machines running MS Server 2003 and 2008, > all VMware guests. I can reproduce this as well. I also found the patch which introduced the problem, but it's not clear yet, why. Stay tuned. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |