See https://bugzilla.redhat.com/show_bug.cgi?id=1826233 Basically, ods-enforcerd daemonizes but then in the background creates the socket for communication. This results in init systems starting the daemon and thinking it is available, while the communication socket is missing. While a hack to the systemd service script is described, it would be nicer if the ods-enforcerd code would create the socket, then daemonizes, so that applications using the socket will block on the socket until the daemon is ready. Paul _______________________________________________ Opendnssec-user mailing list [email protected] https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
[Opendnssec-user] ods-enforcer startup race condition
Paul Wouters via Opendnssec-user Wed, 29 Apr 2020 09:05:19 -0700
