Hello,
I like to have to very tidy and organized file structures. However, sometimes
this results in very long pathnames like
"/home/sstewartgallus/root/home/documents/public/programming/projects/websites/pally/pally/run/pally.sock"
that very old APIs such as bind cannot necessarily handle. There is an ugly
hack to work around this by opening the current working directory with open(".",
0), changing into the directory name that would hold the socket file (in this
case
"/home/sstewartgallus/root/home/documents/public/programming/projects/websites/pally/pally/run"),
binding the socket using a relative path and then changing back into the old
directory. Is this hack too ugly to implement with uwsgi currently? Also, is
there a way to use a pipe instead of a unix domain socket?
Thank you,
Steven Stewart-Gallus
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
