From: mricon at kernel.org (Konstantin Ryabitsev)
Subject: The road to v0.10.1 or v0.11
Date: Fri, 17 Jan 2014 14:29:19 -0500 [thread overview]
Message-ID: <52D9848F.1070308@kernel.org> (raw)
In-Reply-To: <CAHmME9qT73-O82yNTHkc2YOGzRiz5-j8GbapHw2QnQkDw5=eAQ@mail.gmail.com>
On 17/01/14 01:22 PM, Jason A. Donenfeld wrote:
>> But scan for repos is caught by the cache most of the time, and
>> > presumably even if we run persistently we still need to do that
>> > periodically (or use inotify); or do we just rely on the process being
>> > replaced when the set of repositories changes?
> Generally the idea is you restart the fcgi process when things change,
> or at least send it a SIGUSR1. But we could be fancy and support
> inotify/kqueue...
The process that updates the repositories may not have permissions to
send SIGUSR1 to the fcgid process -- either because they are running as
different users or because there are SELinux policies preventing it.
It's really best if cgit recognizes when things like projects.list have
changed.
Best,
--
Konstantin Ryabitsev
Senior Systems Administrator
Linux Foundation Collab Projects
Montr?al, Qu?bec
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 713 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20140117/49ddb4b9/attachment-0001.asc>
next prev parent reply other threads:[~2014-01-17 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 16:12 Jason
2014-01-17 16:28 ` john
2014-01-17 16:38 ` Jason
2014-01-17 16:53 ` john
2014-01-17 18:22 ` Jason
2014-01-17 19:29 ` mricon [this message]
2014-01-17 19:32 ` john
2014-01-17 22:37 ` Jason
2014-01-17 22:36 ` Jason
2014-01-17 17:09 ` Jason
2014-01-17 17:38 ` john
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=52D9848F.1070308@kernel.org \
--to=cgit@lists.zx2c4.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 NNTP newsgroup(s).