Remove or at least reevaluate the suggestion of as-limit-128

[django@…]

​https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/uwsgi/

On Ubuntu 12 LTS, as-limit-128 causes uwsgi to fail with misleading errors like:

libgcc_s.so.1 must be installed for pthread_cancel to work
DAMN ! worker 1 (pid: 29232) died, killed by signal 6 :( trying respawn ...

I wasted hours recompiling uwsgi, looking for path issues with libgcc_s.so.1 and LD, etc.

I removed as-limit=128 and the problem went away. I probably could have increased as-limit as well.

[alextreme]

The option isn't required and the uWSGI documentation doesn't seem to recommend it:

​http://uwsgi-docs.readthedocs.org/en/latest/Options.html#limit-as

In my opinion it is best to not have the option in the example, we shouldn't provide an example that won't work for projects >128MB without a clear reason.

Added a patch to remove the 'limit-as' option from the uWSGI example in the documentation.

[Aymeric Augustin]

Since many people will just copy-paste the example it's best to keep it as minimal as possible.

One might argue that as-limit is a security requirement; I'm not sure.

Anyway, removing that line appears to be a reasonable step at this point.

[Aymeric Augustin <aymeric.augustin@…>]

In be826aafacb9fe266209604116efe128a0b4cdc0:

Fixed #20402: removed as-limit from uWSGI example.

It can fail in hard-to-diagnose ways.