2013/11/4 Roberto De Ioris <[email protected]>

Hi Roberto,
thanks for your answer


> be sure your binary is compiled with pcre support (on recent uWSGI
> releases a warning is printed, and starting from 1.4 a report of the
> feature is printed after build).
>

python setup.py install

prints:

 ################# uWSGI configuration #################

kernel = Linux
malloc = libc
matheval = False
locking = pthread_mutex
ini = True
event = epoll
pcre = False
snmp = True
capabilities = False
yaml = True
json = False
multicast = True
routing = False
ldap = False
sqlite3 = True
zeromq = False
xml = libxml2
udp = True
execinfo = False
ifaddrs = True
ipv6 = False
ssl = True
filemonitor = inotify
alarm = False
timer = timerfd
threading = True
plugin_dir = .
debug = False
async = True
spooler = True
minterpreters = True

############## end of uWSGI configuration #############

... uhm, it seems it is not enabled (see "alarm = False")

lets try to enable pcre...

yum install pcre-devel
python setup.py install

tada, it works!
thank you!


> To be sure you config is valid (read: it is not using invalid options) add
>
> strict = true
>
> on top
>

usefull option!

I modified my ini file adding (on top)

strict = true

but it has no effect (on uwsgi-1.4.10)
(even adding pippo = ciao in the ini file, does not print anything on uwsgi
log)

Marco
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to