Welcome! Log In Create A New Profile

Advanced

Re: Invalid parsed value for keys_zone. Is this a problem?

January 18, 2011 09:44AM
On Tue, Jan 18, 2011 at 04:29:16PM +0200, Eugaia wrote:

> Hi,
>
> On 18/01/2011 16:20, Igor Sysoev wrote:
> > 10485760000 is 0x271000000 in hex. On 32-bit platform it's truncated to
> > 0x71000000, i.e., 1895825408. Yes, it should be checked.
> >
> Also, would it not be better to use off64_t or some other larger type
> for storing the max_size of the cache (or indeed for parsing off's in
> general)? I'm not sure about all Posix systems, but on Debian off_t is
> long int, hence a 32-bit value on 32-bit systems. I've not checked in
> the code, but I'm assuming that the max size of a file cache on 32-bit
> systems may then be 2GB.

nginx uses 64-bit offsets on Linux with
#define _FILE_OFFSET_BITS 64


--
Igor Sysoev
http://sysoev.ru/en/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
Subject Author Posted

Invalid parsed value for keys_zone. Is this a problem?

caruccio January 18, 2011 08:35AM

Re: Invalid parsed value for keys_zone. Is this a problem?

Igor Sysoev January 18, 2011 09:24AM

Re: Invalid parsed value for keys_zone. Is this a problem?

Eugaia January 18, 2011 09:32AM

Re: Invalid parsed value for keys_zone. Is this a problem?

Igor Sysoev January 18, 2011 09:44AM

Re: Invalid parsed value for keys_zone. Is this a problem?

Eugaia January 18, 2011 10:12AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 153
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