Context Navigation

Changes between Version 1 and Version 2 of Ticket #237, comment 8

v1	v2
1	1	Yes, that's exactly what I'm requesting: a supported, documented way to pass in file descriptors for sockets.
2	2
3		Using ~~NGINX~~ directly with systemd is troublesome because a mismatch between the system socket and the "listen" directive causes nginx to ignore the systemd socket and try to open the socket itself. It ignores the systemd socket quietly because it sees the socket as an inherited one that's no longer in use in the current configuration. And, it's impossible to add better error reporting without distinguishing between sockets in the configuration that should ''always'' be inherited from ones that ''might'' be inherited because of internal hand-off during a reload.
	3	Using the NGINX environment variable directly with systemd is troublesome because a mismatch between the system socket and the "listen" directive causes nginx to ignore the systemd socket and try to open the socket itself. It ignores the systemd socket quietly because it sees the socket as an inherited one that's no longer in use in the current configuration. And, it's impossible to add better error reporting without distinguishing between sockets in the configuration that should ''always'' be inherited from ones that ''might'' be inherited because of internal hand-off during a reload.
4	4
5	5	My patches attempt to resolve this by providing a straightforward, non-redundant way to outsource a listener in nginx's configuration to an inherited systemd socket.