Hello!
On Sun, Aug 18, 2013 at 05:29:11PM -0400, B.R. wrote:
[...]
> > > Testing conf is of course a duplicate of work, but that's a safe
> > operation.
> > > The command output will determine if your new configuration will work
> > > without having to carefully watch logs with anxiety.
> >
> >
Hello,
On Sun, Aug 18, 2013 at 3:14 PM, Maxim Dounin wrote:
>
> Making any changes to the configuration isn't something
> significant: even without changes at all new binary on disk might
> not consider an old configuration as a valid e.g. due to some
> module not compiled in. And a reload migh
Hello!
On Sat, Aug 17, 2013 at 12:36:38PM -0400, B.R. wrote:
> Hello,
>
>
> On Sat, Aug 17, 2013 at 7:37 AM, Maxim Dounin wrote:
>
> > Hello!
> >
> > I don't think that calling "nginx -t" as a mandatory step before
> > configuration reload is a good idea: nginx binary running and
> > nginx bi
Hello,
On Sat, Aug 17, 2013 at 7:37 AM, Maxim Dounin wrote:
> Hello!
>
> I don't think that calling "nginx -t" as a mandatory step before
> configuration reload is a good idea: nginx binary running and
> nginx binary on disk might be different, and "nginx -t" result
> might be incorrect because
Hello!
On Sat, Aug 17, 2013 at 12:07:22AM -0400, B.R. wrote:
> Hello Maxim! :o)
>
>
> On Fri, Aug 16, 2013 at 11:16 PM, Maxim Dounin wrote:
>
> > Hello!
> >
> > On Fri, Aug 16, 2013 at 10:16:16PM -0400, B.R. wrote:
> >
> > > I guess it would be nice if the doc warned about directives that nee
Hello Maxim! :o)
On Fri, Aug 16, 2013 at 11:16 PM, Maxim Dounin wrote:
> Hello!
>
> On Fri, Aug 16, 2013 at 10:16:16PM -0400, B.R. wrote:
>
> > I guess it would be nice if the doc warned about directives that need a
> > server restart to be reloaded.
> >
> > Everyone supposes (as it seems obvio
Hello!
On Fri, Aug 16, 2013 at 10:16:16PM -0400, B.R. wrote:
> I guess it would be nice if the doc warned about directives that need a
> server restart to be reloaded.
>
> Everyone supposes (as it seems obvious) that reloading Nginx is enough to
> apply configuration changes.
Reloading is enoug
I guess it would be nice if the doc warned about directives that need a
server restart to be reloaded.
Everyone supposes (as it seems obvious) that reloading Nginx is enough to
apply configuration changes.
An interesting part of the question was the inquiry about the potential
existence other dir
Hello!
On Thu, Aug 15, 2013 at 11:07:30PM +0800, li zJay wrote:
> Hello:
>
> I found that some nginx config option doesn't take effect after
> modification with reload, the following is a simple test case:
>
> nginx version: nginx/1.2.7
> nginx.conf:
>
> worker_proc
Hello:
I found that some nginx config option doesn't take effect after
modification with reload, the following is a simple test case:
nginx version: nginx/1.2.7
nginx.conf:
worker_processes 1;
error_log logs/error.log info;
events {
worker_connections 1024;
}
10 matches
Mail list logo
