On 12/02/15 10:15, Antoine Jacoutot wrote:
On Wed, Dec 02, 2015 at 10:12:56AM +0100, Martijn van Duren wrote:
Hello ports@,
currently when nginx is issued a reload command it simply sends a dumb
SIGHUP, but without checking if the reload is loaded correctly. Since nginx
keeps running one might
On 2015/12/02 10:15, Antoine Jacoutot wrote:
> On Wed, Dec 02, 2015 at 10:12:56AM +0100, Martijn van Duren wrote:
> > Hello ports@,
> >
> > currently when nginx is issued a reload command it simply sends a dumb
> > SIGHUP, but without checking if the reload is loaded correctly. Since nginx
> > kee
Hello ports@,
currently when nginx is issued a reload command it simply sends a dumb
SIGHUP, but without checking if the reload is loaded correctly. Since
nginx keeps running one might get the impression that the reload was
successful.
Would it make sense to check the validity of the configu
On Wed, Dec 02, 2015 at 10:12:56AM +0100, Martijn van Duren wrote:
> Hello ports@,
>
> currently when nginx is issued a reload command it simply sends a dumb
> SIGHUP, but without checking if the reload is loaded correctly. Since nginx
> keeps running one might get the impression that the reload w