This is the forever loop that it it running in the script
for {
nginx -s reload //without the port
nginx -s reload //with the port
}
I found there was a transient that both the master process and the newly forked
worker were listening the same port, I am not sure if this mgiht cause the
"bind" error.
Another fact is that the port is listening after the "bind" error was
occurring, so this was not due to the "delete" was not completed that makes the
"add" not success.
I am wondering how this "bind" error happens?
Br,
Allen_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
