Tell me your feature request about nginx

Server NGINX
21

On 6/13/08, Aleksandar L. [email protected] wrote:

Why not reusing the current feature site?

Aleks

On the wiki? I guess I’m fine with that. Be cooler to have some sort
of voting/commenting mechanism per request…

I assume you mean this… it’s a little unstructured for me personally
:slight_smile:
http://wiki.codemongers.com/NginxFeatureRequests

22

On 6/13/08, Jure Pečar [email protected] wrote:

Ideally this should work the way mod_backhand works for apache 1.3. Nginx should make its list of upstream servers accesible via some API and some external process that monitors those servers should be able to dinamically add or remove them from nginx’s view. External process should have a way to figure out various parameters from workers (either some addon to workers or some acompanying daemon that monitors the worker hardware node) and deceide on the best list based on different decision weights from the list of those parameters.

See http://www.backhand.org/mod_backhand/

I’m pretty sure this would meet almost everyone’s needs… and if it
could be integrated with something like ldirectord, I’m all for it.
The healthchecking and notification to nginx when to bring up/down
upstreams I think is the missing ingredient to using it fully for load
balancing.

Another note:

We should get a site started here with a list of ideas and then a way
for people to vote/second them - to get a true priority list of what
people want and a full list of everything people have asked for…

23

On Fre 13.06.2008 08:56, mike wrote:

:slight_smile:
http://wiki.codemongers.com/NginxFeatureRequests

Hm, yes would be nicer. Is there a ‘easy,secure’ SW for this, so that
you not must install the next big, blown CMS.

Aleks

24

the only quick voting thing i can think of is something like Pligg,
but it’s full of bugs last I’ve used it. A Digg type clone might be
the best - because it should have built in commenting and built in
voting…

Kubelabs - PHPDug - this one is pretty simple

I’d be willing to host something like this too, if Cliff is too busy.
The only difference is instead of submitting a URL like Digg/clones
expect, you submit a text description. This is actually something I
personally have been wanting to throw together for a project or two at
work as well - a feature/wishlist request engine with comment and
voting support…

25

On Fre 13.06.2008 09:13, mike wrote:

expect, you submit a text description. This is actually something I
personally have been wanting to throw together for a project or two at
work as well - a feature/wishlist request engine with comment and
voting support…

Looks nice, when do you think you are able to setup it?
If it’s ok for you I can make it on this weekend.

Aleks

26

On Fri, 2008-06-13 at 09:13 -0700, mike wrote:

expect, you submit a text description. This is actually something I
personally have been wanting to throw together for a project or two at
work as well - a feature/wishlist request engine with comment and
voting support…

I can look into this later today.

Cliff

27

On Thu, Jun 12, 2008 at 07:08:16PM -0400, Dan M wrote:

runit from Gerrit Pape, etc.
FreeBSD’s newsyslog can be run by cron every minute to rotate logs based
on file size and to keep a predefined number of logs.
There is no sense to log to a pipe to achieve this.
Logging to pipe causes useless context switches, memory copy operations,
and CPU cache trashes:

  1. nginx writes to pipe
    copy operation
    context switch
  2. logger read from pipe
    copy operation
  3. logger writes to file
    copy operation
    context switch

instead of single copy operation.

Drop of root priveleges once it’s bound and chroot as well. Even
Lighttpd does that.

Lighttpd drops root because it handles client connections in single
process.
nginx handles the connections in worker process that run as unprivileged
user.

28

On Fre 13.06.2008 10:40, Cliff W. wrote:

The only difference is instead of submitting a URL like Digg/clones
expect, you submit a text description. This is actually something I
personally have been wanting to throw together for a project or two at
work as well - a feature/wishlist request engine with comment and
voting support…

I can look into this later today.

Cool, thanks.

Aleks

29
  1. Embedded Lua interpreter

+1

On Fri, Jun 13, 2008 at 1:18 PM, Manlio P.

30

Igor S. wrote:

FreeBSD’s newsyslog can be run by cron every minute to rotate logs based
on file size and to keep a predefined number of logs.
There is no sense to log to a pipe to achieve this.
Logging to pipe causes useless context switches, memory copy operations,
and CPU cache trashes:

Gotcha. Thanks.

socklog then: http://smarden.org/socklog/benefits.html