From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69033 invoked by alias); 12 May 2019 14:30:53 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 69014 invoked by uid 89); 12 May 2019 14:30:46 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy=linda, officially, cents, regulate X-HELO: Ishtar.sc.tlinx.org Received: from ishtar.tlinx.org (HELO Ishtar.sc.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 12 May 2019 14:30:45 +0000 Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id x4CEUYd4066163 for ; Sun, 12 May 2019 07:30:36 -0700 Message-ID: <5CD82E0A.7010002@tlinx.org> Date: Sun, 12 May 2019 14:30:00 -0000 From: L A Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: SSHD Service shuts down after a while after latest library updates References: <110c51d9-507c-afbb-df37-bc48b7d847c3@gmx.de> In-Reply-To: <110c51d9-507c-afbb-df37-bc48b7d847c3@gmx.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-05/txt/msg00095.txt.bz2 On 5/12/2019 6:35 AM, Enrico.Bertram wrote: > \ > > The service is configured to start automatically and does so on each reboot. > The event viewer does not show any event (for example the "stopped" on > normal shutdowns) - the service is just in shut down state every now and > then and I have to manually start it again. > This has been a feature of Windows since win98. Not officially, mind you, but any scheduled task in windows would eventually become unscheduled and stop running with out any notification. The only way I found to get round this is by having a job login from a reliable server (like linux) multiple times/hour with a control login that attempts to remain logged in so that problems can be solved by the already logged in process. For the first time since Win98, I'm starting to get error reports when there are problems as well as notifications if there was a problem resetting my basic state. I may have to extend my monitoring and corrections since some are more involved, but sadly it was the only way I found out how to get prompt errors when things stopped working because Windows philosophy is to not report things in hope that the problem or need for the report will go away. Part of this stems from, for example in tools to regulate resources given to programs, only servers are allowed to do so, with the regulating software not running on Windows. There are some unsatisfactory third party options (Process Lasso) that do things like keep processes running or restart if they die -- things that the Windows service manager claims to do, but not always work. Windows on my machine hasn't been able to start the system log function for about 2-3 years -- with MS having no clue and only recommendation being to upgrade to win10. I have a few problem the MS was unable to solve for more than 3 years with similar outcomes. Very often the problems aren't fixed, but appear to be so because some do not trigger frequently. So if you want reliable debug and monitoring, use another OS like linux to monitor the flakey windows. (my 2 cents).... Linda -- 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