This is the mail archive of the
mailing list for the Cygwin project.
Re: calm now runs on-demand
- From: Jon Turney <jon dot turney at dronecode dot org dot uk>
- To: cygwin-apps at cygwin dot com
- Date: Sat, 1 Jul 2017 15:04:11 +0100
- Subject: Re: calm now runs on-demand
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com> <a2d4b3d6-b7a9-8be4-f17c-d2fd94d3df9d-GrJqePx9RPPAJUdA+FbntA@public.gmane.org> <20170418110549.GE30642@calimero.vinschen.de> <firstname.lastname@example.org>
On 01/07/2017 12:31, Andrew Schulman wrote:
On Apr 17 12:34, Jon Turney wrote:
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
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
I have upload access, but AFAIK not shell access. I think most maintainers
don't, unless that's changed.
Correct. But unless you have shell access to make changes by directly
moving files around on sourceware, you don't need shell access to run calm.
Currently, calm runs (i) if a !ready file exists in your upload area
when your sftp session closes, and (ii) at 00:10 UTC and every 4 hours