Hi,
let assume that we run the following domains:
- agoodexample.org
- agoodexmaple.com
- agoodexample.net
- a-good-example.org
- a-good-example.com
- a-good-example.net
Our main site should be www.a-good-example.com -- people coming from any
other mentioned domain/combination should be re
H
i
>
> After a 60 seconds timer was fired and client connection was
>
> closed as timed out.
>
> Yeah. That's what I feared. But the connection was definitely still
> open and data was being transferred.
You are still testing through your 2G GSM connection, right?
How can you be sure that this c
H
i,
I would really wonder if you would see a real difference between using a
tmpfs or not for the webserver's tmp body location. A tmpfs is only faster,
but as long as your storage has enough free IO resources and is fast enough
to actual write the data, you shouldn't notice.
And keep in mind: Yo
Hi,
you are right. There is a problem:
https://bugs.gentoo.org/show_bug.cgi?id=473036
Upstream (nginx) accepted the report:
http://trac.nginx.org/nginx/ticket/376
--
Regards,
Igor
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mail
Hi,
can you tell use the HDD modell you are currently using? And are you
using real dedicated servers or some kind of virtualization?
Current SATA disks (Seagate ST1000DM-003 for example) are able to
provide an avg speed of 190MB/s (keep in mind: It's their avg speed.
So when the disk is full, th
Hi,
> Any other ideas?
Not sure if relevant, but in Gentoo's bug tracker are some open bugs
regarding current logrotate versions:
https://bugs.gentoo.org/show_bug.cgi?id=476202
https://bugs.gentoo.org/show_bug.cgi?id=474572
https://bugs.gentoo.org/show_bug.cgi?id=476720
Seems to be upstream bug
Hi,
and don't forget system's page cache. From my experience:
The files needed to process the first request aren't yet read, so
Linux has to read them from disk (slow).
Then, for the second and further requests, the files are in the page
cache (aka system buffer), so that Linux don't have to rea
