On Wed, 30 Jul 2014 00:37:47 +0100
Laurent Bercot wrote:
> On 29/07/2014 20:59, Jan Pobrislo wrote:
> > There are two possible resolutions - either make runsv create new
> > pipe when asked to start up again or make it die since it's unable
> > to spawn a child.
>
> Actually, there's only one
On Tue, Jul 29, 2014 at 10:16:55PM +0200, Jérémie Courrèges-Anglas wrote:
> This is a follow-up for a report sent by Mike in April. The problem
> here is that on some platforms such as OpenBSD and NetBSD, time_t has
> been enlarged to 64 bits even on ILP32. Since time_t is already used in
> the r
On Thu, 24 Jul 2014, Alex Efros wrote:
> Hi!
>
> Is it possible to run nginx under runsv supervision without breaking
> nginx's ability to upgrade (SIGUSR2) or reload config (SIGHUP) gracefully
> without interrupting current connections?
I get this in nginx's error.log file when I do 'sv 2 /ser
