Overriding configuration variables, specifically access_log

Igor Sysoev igor at sysoev.ru
Thu Aug 18 17:01:36 UTC 2011

On Thu, Aug 18, 2011 at 12:36:30PM -0400, Adam Nelson wrote:
> We are using nginx/1.0.5 from the nginx apt repositories and have noticed
> that when setting the access_log directive in /etc/nginx/conf.d/common, it
> does nothing unless I comment out the access_log directive above it in
> /etc/nginx/nginx.conf.
> It appears that the variable is evaluated only the first time in any given
> block (in this case inside the http { } block) and cannot be overridden.  Is
> that the case?
> If so, I think the best solution is to move the access_log directive inside
> each of the individual location { } blocks where I need it so as not to
> interfere with the stock nginx.conf file.
> The only other alternative I can think of is to overwrite the nginx.conf
> file entirely - I'm concerned about doing that because I don't want that
> file overwritten by the nginx aptitude installer in the future.
> Does anybody have a good solution to this?

You can set several access_log files on a level, so this is the reason
why you can not override it.

Igor Sysoev

More information about the nginx mailing list