delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2019/05/12/10:31:04

X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:message-id:date:from:mime-version:to:subject
:references:in-reply-to:content-type:content-transfer-encoding;
q=dns; s=default; b=bO6PuKQPkCeYJ8uuds9EDXawPJhcL629hqZchnpYpeu
JE/wwH7N7QsbFYn8ZdPUSiO3KUlDfJXpPKVkdmknb50YUa1eUUWaZKDi/F3AfbHW
IUpciycntRZ8+pj3nmh4kyX9iqzczZWskX7o8Rz9hSGGB7zO3mLwho7oMcZ7sWpg
=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:message-id:date:from:mime-version:to:subject
:references:in-reply-to:content-type:content-transfer-encoding;
s=default; bh=G8LRq79zwzVtHZrqvgNd0iHsbCA=; b=e3Rf/1j62SdiPk3lK
P7xwdQW4l9Ie0am9Jlmr8xe2P+/YOV4MtYTYLRlZvDljUwiLQ5LhBlkPTrQUdKNg
LNoiGmjulpoTmNzHDmNi5UWEcdmM99Av77nyO3Ciwb8dg+9H9oYo8Cy9drozfxdI
7adutOCIOnpwrCGfGtOSof42Mw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
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
Message-ID: <5CD82E0A.7010002@tlinx.org>
Date: Sun, 12 May 2019 07:30:34 -0700
From: L A Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: SSHD Service shuts down after a while after latest library updates
References: <110c51d9-507c-afbb-df37-bc48b7d847c3 AT gmx DOT de>
In-Reply-To: <110c51d9-507c-afbb-df37-bc48b7d847c3@gmx.de>
X-IsSubscribed: yes

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019