> In the past, we've faced issues with tomcat when starting it -- the > service tomcat6 start would return even if the applications weren't > loaded yet, so any HTTP/ajp request would fail. See the lsof hack in > spacewalk-service. How is this issue addressed in the proposed systemd > approach?
The current approach doesn't address this, but we could use systemd's socket functionality: systemd itself is able to open the socket and queue incoming requests, only releasing them for processing when the consumer side (tomcat6) comes up -- xinetd style. Would this be acceptable? -- Pablo N. Hess RHCA, RHCVA, RHCX, RHCI, RHCE Instructor - Red Hat ph...@redhat.com +55 11 9325-3016 PGP fingerprint: D34B F26B A96F 3CFC 87CE 3F23 12F3 05F3 1CF9 5486 _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
