Hello,
On Wed, Jun 5, 2013 at 1:56 AM, shahzaib shahzaib wrote:
> Hello,
>
>We're using nginx-1.2.8 to stream large files size 1G but found the
> slow stream with high utilization of harddrive using command "iostat -x -d
> 3"
>
> Device: rrqm/s wrqm/s r/s w/s rse
Hello,
We're using nginx-1.2.8 to stream large files size 1G but found the
slow stream with high utilization of harddrive using command "iostat -x -d
3"
Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s
avgrq-sz avgqu-sz await svctm %util
sdc 0
So ulimit in the init script is redundant.
I'll use worker_rlimit_nofile.
Thanks
On Tue, Jun 4, 2013 at 5:35 PM, Sergey Budnevitch wrote:
>
> On 4 Jun2013, at 17:32 , pablo platt wrote:
>
> > "worker_rlimit_nofile set RLIMIT_NOFILE for workers only, so master
> process still sees previous
Hello Nginx users,
Now available: Nginx 1.5.1 for Windows http://goo.gl/eeXMm (32-bit and
64-bit versions)
These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are at
nginx.org.
Announcements are also availabl
Andrew Alexeev wrote in post #1083715:
> Dave,
>
> On Nov 9, 2012, at 1:14 PM, Dave Nolan wrote:
>
>>> If you want the flexibility of DNS resolving and safeguard yourself
>> else. I'm just interested in why it's not, and whether there are plans
>> to change it. We might be interested in sponsoring
On 4 Jun2013, at 17:32 , pablo platt wrote:
> "worker_rlimit_nofile set RLIMIT_NOFILE for workers only, so master process
> still sees previous value."
> http://mailman.nginx.org/pipermail/nginx/2008-April/004596.html
You hardly need to increase number of file descriptors for master process,
Changes with nginx 1.5.1 04 Jun 2013
*) Feature: the "ssi_last_modified", "sub_filter_last_modified", and
"xslt_last_modified" directives.
Thanks to Alexey Kolpakov.
*) Feature: the "http_403" parameter of the "proxy_next_upstream",
"worker_rlimit_nofile set RLIMIT_NOFILE for workers only, so master process
still sees previous value."
http://mailman.nginx.org/pipermail/nginx/2008-April/004596.html
If worker_rlimit_nofile doesn't affect the master process and limits.conf
doesn't affect init script, do I need to call ulimit in
On 4 Jun2013, at 17:04 , pablo platt wrote:
> It's not clear to me how worker_rlimit_nofile, /etc/security/limits.conf and
> setting ulimit in the init.d script are related.
>
> Is worker_rlimit_nofile the same as using ulimit in the init.d script?
> Or does ulimit sets the maximum limit and
On 4 Jun2013, at 16:39 , Maxim Dounin wrote:
> Hello!
>
> On Tue, Jun 04, 2013 at 04:30:40PM +0400, Sergey Budnevitch wrote:
>
>>
>> On 4 Jun2013, at 15:39 , pablo platt wrote:
>>
>>> Hi,
>>>
>>> I'm using the ubuntu package from nginx.org.
>>>
>>> In the package from the official ubunt
It's not clear to me how worker_rlimit_nofile, /etc/security/limits.conf
and setting ulimit in the init.d script are related.
Is worker_rlimit_nofile the same as using ulimit in the init.d script?
Or does ulimit sets the maximum limit and worker_rlimit_nofile the limit
per worker?
Why does the in
2013/6/4 Sergey Budnevitch :
> No. I will try to wait until either systemd or upstart win. :-)
In case you want to support other distros than Ubuntu, you should have
an eye on SystemD …but this is Off-Topic here.
Regards, Andre
___
nginx mailing list
n
Hello!
On Tue, Jun 04, 2013 at 04:30:40PM +0400, Sergey Budnevitch wrote:
>
> On 4 Jun2013, at 15:39 , pablo platt wrote:
>
> > Hi,
> >
> > I'm using the ubuntu package from nginx.org.
> >
> > In the package from the official ubuntu repo, you can set file descriptor
> > limit by changing /
On 4 Jun2013, at 15:39 , pablo platt wrote:
> Hi,
>
> I'm using the ubuntu package from nginx.org.
>
> In the package from the official ubuntu repo, you can set file descriptor
> limit by changing /etc/default/nginx
> # Check if the ULIMIT is set in /etc/default/nginx
> if [ -n "$ULIMIT" ];
Hi,
I'm using the ubuntu package from nginx.org.
In the package from the official ubuntu repo, you can set file descriptor
limit by changing /etc/default/nginx
# Check if the ULIMIT is set in /etc/default/nginx
if [ -n "$ULIMIT" ]; then
# Set the ulimits
ulimit $ULIMIT
fi
Is there a reaso
Hello!
On Tue, Jun 04, 2013 at 12:52:03AM -0400, justin wrote:
> Does it seem reasonable that the 499 status codes are responsible for double
> requests? I.E. do you think the client is resending the request after the
> 499 status?
No. But both 499 status codes (i.e. client closed connection) a
Hello!
On Mon, Jun 03, 2013 at 07:07:50PM -0400, kgoess wrote:
> We're using nginx as a middle layer in front of our application server
> (mod_perl). When mod_perl returns an error page, the HTTP status line is
> missing the "reason phrase" after the status code, like "Not Found", e.g.
>
> HTTP
Hello!
On Mon, Jun 03, 2013 at 03:24:52PM -0700, Alder Network wrote:
> I got nginx websocket proxy working but the socket would close
> in a minute or so. So I add
> proxy_read_timeout 180s;
> and it works within 3 minutes but closed the websocket after 3
> minutes, but it works OK before that
Thanks Maxim and Jonathan for making these things clear to me!
Disabling disk buffering by using fastcgi_max_temp_file_size 0; and reducing
the number of buffers solved the problem and made my service more
efficient.
Best Regards,
Belly Dancer
Posted at Nginx Forum:
http://forum.nginx.org/read.p
19 matches
Mail list logo
