Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <98fe46fd05051110472fca0846@mail.gmail.com> Date: Wed, 11 May 2005 13:47:44 -0400 From: Henri Dupre Reply-To: Henri Dupre To: cygwin AT cygwin DOT com Subject: error: fork: after recent updates with sshd Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j4BHm6OG032120 I had that problem in the past on our old server and it happened after certain updates and now it happened again on our new server after some recent cygwin updates. I have the sshd server installed as service on the server (Win 2000 server sp4, all latests patches installed). The server is running ISA 2000 and is used as proxy for internet. After a reboot I am having now this strange sshd error message: Impossible de trouver la description de l'ID d'événement ( 0 ) dans la source ( sshd ). L'ordinateur local n'a peut-être pas les informations de Registre nécessaires ou les fichiers DLL de messagerie pour afficher les messages provenant d'un ordinateur distant sshd : PID 1828 : error: fork: Resource temporarily unavailable. The strangest thing is that the sshd server works after a service restart. And it used to work flawlessly. I read in the mailing list about the possible lack of memory but the server has 2go ram and 4 go virtual memory so I doubt that it is the issue. What other issues can be involved? Thanks, Henri. -- 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/