> AFAIK there's no way to have the kernel notify you of when a different process starts listening on a port.
For startup, I’d argue the proper way is for the process to bind the socket before forking as a daemon.
With such a design, one can launch a list of dependent processes without worrying how long they each take to start up. No polling loops needed!
Of course, that requires some careful design — “fork and forget” is too appealing. The process would be responsible for creating its PID file after forking but the socket before…
Alternatively, an IPC notification could be used but would require some sort of standardization to be generally useful.
For startup, I’d argue the proper way is for the process to bind the socket before forking as a daemon.
With such a design, one can launch a list of dependent processes without worrying how long they each take to start up. No polling loops needed!
Of course, that requires some careful design — “fork and forget” is too appealing. The process would be responsible for creating its PID file after forking but the socket before…
Alternatively, an IPC notification could be used but would require some sort of standardization to be generally useful.