Novy, Ondrej
July 21, 2015 09:24AM
Hi,

21. 7. 2015 v 15:13, Valentin V. Bartenev <vbart@nginx.com<mailto:vbart@nginx.com>>:
What's the problem with signaling nginx to reload configuration?

It’s use-case problem for us.

We have geoip-data (deb) package, which contains GeoIP database. This package is universal, and don’t know usage of contained database. It’s not logical to do ngnix reload in post-install script in this package, because it’s general package. Auto reload of database is better solution in this situation.

I'm asking because you're suggesting a patch that adds another configuration
option which potentially can affect performance.

that’s true. But shouldn’t this decision be on admin? If it’s option in GeoIP lib, why not allow to use it in nginx?

Ondřej Nový
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

[PATCH] geoip_check_cache option

Anonymous User 826 July 20, 2015 12:14PM

Re: [PATCH] geoip_check_cache option

Valentin V. Bartenev 360 July 20, 2015 12:46PM

Re: [PATCH] geoip_check_cache option

Novy, Ondrej 350 July 20, 2015 01:44PM

Re: [PATCH] geoip_check_cache option

Valentin V. Bartenev 341 July 21, 2015 09:14AM

Re: [PATCH] geoip_check_cache option

Novy, Ondrej 416 July 21, 2015 09:24AM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 128
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready