From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: calm now runs on-demand
Date: Sat, 01 Jul 2017 14:04:00 -0000 [thread overview]
Message-ID: <c58e095a-b98e-4c88-eba7-48fa4ab043d2@dronecode.org.uk> (raw)
In-Reply-To: <ou1flcpvf0k6v8fqr9at4cbea8vhu07ppj@4ax.com>
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
>>> 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.
>
> 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
thereafter.
next prev parent reply other threads:[~2017-07-01 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 11:34 Jon Turney
2017-04-18 11:05 ` Corinna Vinschen
2017-07-01 11:31 ` Andrew Schulman
2017-07-01 14:04 ` Jon Turney [this message]
2017-07-03 16:05 ` Andrew Schulman
2017-07-01 5:18 ` Marco Atzeri
2017-07-01 13:54 ` Jon Turney
2017-07-01 14:14 ` Marco Atzeri
2017-07-01 14:22 ` Jon Turney
2024-04-01 22:46 ` Jon Turney
2017-07-01 14:00 ` Achim Gratz
2017-07-01 14:03 ` Achim Gratz
2017-07-01 14:16 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c58e095a-b98e-4c88-eba7-48fa4ab043d2@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).