2012/9/17 Roberto De Ioris <[email protected]>:
>
>> I found:
>> http://forum.nginx.org/read.php?2,200086,200139#msg-200139
>> and:
>> http://lists.unbit.it/pipermail/uwsgi/2011-June/002130.html
>>
>> When I start uWSGI with:
>> socket = @uwsgi-test
>>
>> I have:
>> uwsgi socket 0 bound to UNIX address @uwsgi-test fd 3
>>
>> but:
>> netstat -n | grep -i uwsgi
>
>
> netstat -l here, as you need to get listening sockets
>
my oversight :P should be: netstat -ln | grep -i uwsgi
>
>>
>> and at exit:
>> goodbye to uWSGI.
>> unlink(): No such file or directory [core/uwsgi.c line 1208]
>
Now it works well.
>
> this is a harmless bug, triggered by vacuum. (it tries to unlink a
> non-existent file) Fixed in latest tip.
>
>>
>>
>> Is this patch has been applied in Nginx?
>> As it is to work with @ or \0 ?
>> I could not connect uWSGI and Nginx using this type of Socket.
>>
>
> It has never been applied to official tree, and honestly i do not remember
> why (maybe because no-one agreed between \0 and @) but my patch should
> still apply.
>
>From what I understand, Nginx uses @ to create an abstract internal
names for locations. for example:
try_files /system/maintenance.html $uri $uri/index.html $uri.html @mongrel;
location @mongrel {
proxy_pass http://mongrel;
}
And Igor Sysoev do not want to mix this with unix:@socket_name.
Therefore, suggested a different marking (\0), but no agreement was reached.
In total, \0 is not such a tragedy. I'll try to resume the subject.
--
Łukasz Wróblewski
http://www.nri.pl/ - Nowoczesne Rozwiązania Internetowe
http://www.hostowisko.pl/ - Profesjonalny i tani hosting
http://www.katalog-polskich-firm.pl/ - Najlepszy darmowy katalog firm
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
