Why not remove UNIX domain socket before bind
Shuxin Yang
shuxinyang.oss at gmail.com
Wed Nov 30 07:39:39 UTC 2016
Hi, Datong:
I don't think fixing #753 resolves all the trouble: it does not help
for scenario 1 at all. For scenario 2, it only help if nginx is
terminated by SIGQUIT; however, Nginx could be killed by other signals,
say SIGKILL.
Thanks
Shuxin
On 11/29/2016 11:11 PM, Datong Sun via nginx-devel wrote:
> Hello Shuxin,
>
> I have seen the same issue before. As far as I can tell this is simply
> a bug instead of by design (correct me if I'm wrong). I can also
> confirm that nginx will leave behind the listening socket file when
> terminated with SIGQUIT. There has been a bug report opened more than
> a year ago (https://trac.nginx.org/nginx/ticket/753) but still not
> being fixed.
>
> Thanks,
> Datong
>
> On Tue, Nov 29, 2016 at 1:30 PM, Shuxin Yang <shuxinyang.oss at gmail.com
> <mailto:shuxinyang.oss at gmail.com>> wrote:
>
> Hi, There:
>
> Is there any reason not to delete UNIX domain socket before
> bind? It is bit inconvenient when :
>
> 1). debugging: previous debugging session quit prematurely without
> erasing the UNIX domain socket, and the subsequent debugging
> session only see "address already in use" error message, and have
> to delete the socket, and launch debugger again.
>
> 2). Writing deploy script. We need to make sure UNIX domain
> sockets are completely delete before launching Nginx; also care
> must be taken to keep the script and config file in sync, which is
> sometimes bit annoying.
>
>
> Thanks
>
> Shuxin
>
>
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org <mailto:nginx-devel at nginx.org>
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
> <http://mailman.nginx.org/mailman/listinfo/nginx-devel>
>
>
>
>
> --
>
> *Datong Sun* | Systems Engineer
> datong at cloudflare.com <mailto:datong at cloudflare.com>
>
> 1 888 99 FLARE | www.cloudflare.com <https://www.cloudflare.com/>
>
>
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20161129/ad14f339/attachment.html>
More information about the nginx-devel
mailing list