From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jason at zx2c4.com (Jason A. Donenfeld)
Date: Fri, 17 Jan 2014 19:22:21 +0100
Subject: The road to v0.10.1 or v0.11
In-Reply-To: <20140117165333.GN7608@serenity.lan>
References: <CAHmME9p6ubctzVTwRurFW+Vg9fYLwjKAoPr6_MwbKHJiHKv_YA@mail.gmail.com>
 <20140117162851.GM7608@serenity.lan>
 <CAHmME9rUbNW7Jkh2TDiXTJP+Z=+d7SgdgvWp3nPkcwL9ZdPdiQ@mail.gmail.com>
 <20140117165333.GN7608@serenity.lan>
Message-ID: <CAHmME9qT73-O82yNTHkc2YOGzRiz5-j8GbapHw2QnQkDw5=eAQ@mail.gmail.com>

On Fri, Jan 17, 2014 at 5:53 PM, John Keeping <john at keeping.me.uk> 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...