You could set the max upload value to INT_MAX (2^31-1, as you have
below), and that should work, but going higher will be difficult.
Simply changing the variable to a long in one place is insufficient,
because that value is handled in quite a few places, and you'd need to
change all of them;
With 2Gb size of log file all scripts don't work and the log file
don't growing. Only static files are serves
--
Best regards, Alexey Pechnikov.
http://pechnikov.tel/
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com
The log module supports rolling. Normally it is done daily, but if your
logs are growing too quickly and hitting 2G within a day you could set
up a cronjob to send the server a signal to roll the logs, or a
scheduled task within the server to roll the logs every hour, or when
they reach a
2011/5/17 Jeff Rogers dv...@diphi.com:
Undocumented behaviour is bug, isn't it?
--
Best regards, Alexey Pechnikov.
http://pechnikov.tel/
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com with the
body of SIGNOFF
Alexey Pechnikov wrote:
2011/5/17 Jeff Rogersdv...@diphi.com:
Undocumented behaviour is bug, isn't it?
I didn't suggest that it wasn't, I only offered a possible workaround
for you to solve the immediate problem facing you.
There is a bugtracker for aolserver at sf where you can file
