public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
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:22:00 -0000	[thread overview]
Message-ID: <1d410a89-af3f-ddbd-4374-5d681ae7e9ed@dronecode.org.uk> (raw)
In-Reply-To: <386bd3e9-546e-1176-2a3e-697b4467ca6a@gmail.com>

On 01/07/2017 15:14, Marco Atzeri wrote:
> On 01/07/2017 15:54, Jon Turney wrote:
>> On 01/07/2017 06:18, Marco Atzeri wrote:
>>> On 17/04/2017 13:34, Jon Turney wrote:
>>>>
>>>> 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)'.
>>>
>>> Jon,
>>> I have shell access but I do not find calm anywhere.
>>> I assume "~cygwin-admin" is more restricted than shell access.
>>>
>>> As I did change to the relarea for gcc test, how to force the
>>> update of setup.ini's ?
>>
>> I think I have fixed the permissions, so this should work for you now.
>>
>> Thanks for pointing out this problem.
> 
> May be I misunderstood how I should use it
> 
> matzeri@sourceware ~
> $  /home/cygwin/bin/calm scan-relarea
> /home/cygwin/bin/calm: line 13: kill: (14958) - Operation not permitted

No, that's me being dumb.  I guess I need to think some more about how 
to make this work for other users...

  reply	other threads:[~2017-07-01 14:22 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
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 [this message]
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=1d410a89-af3f-ddbd-4374-5d681ae7e9ed@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).