From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 61641 invoked by alias); 17 Apr 2017 11:34:38 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 61298 invoked by uid 89); 17 Apr 2017 11:34:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=SFTP, cygwin-admin, sftp, cygwinadmin X-HELO: out1-smtp.messagingengine.com Received: from out1-smtp.messagingengine.com (HELO out1-smtp.messagingengine.com) (66.111.4.25) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 17 Apr 2017 11:34:35 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B715F207D3 for ; Mon, 17 Apr 2017 07:34:35 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 17 Apr 2017 07:34:35 -0400 X-ME-Sender: Received: from [192.168.1.102] (host86-141-129-28.range86-141.btcentralplus.com [86.141.129.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 601387E2C3 for ; Mon, 17 Apr 2017 07:34:35 -0400 (EDT) From: Jon Turney Subject: calm now runs on-demand To: cygwin-apps@cygwin.com X-Mozilla-News-Host: news://news.gmane.org Message-ID: Date: Mon, 17 Apr 2017 11:34:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-04/txt/msg00043.txt.bz2 I recently deployed an update to calm which should causes it to run on-demand after a maintainer SFTP upload. Hopefully this reduces the inconvenience of having to wait till the next scheduled run, after an upload is made which fails due to some easily correctable problem. calm continues to also run on a schedule at :10 and :40 past the hour, so it will still note changes which have been made directly on sourceware. If you have shell access on sourceware, and make such changes, you can force calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'. Given that, it probably makes sense to consider reducing the frequency of scheduled runs.