On Sun, Apr 21, 2013 at 12:34:13AM +0200, Rune Morling wrote: > Ok, switching to the "unique" port solution works well enough, though it > would be great if conary could effect a "service httpd reload" post > install. What is the most appropriate way to do that? A taghandler for > /etc/conary/config.d/conary-proxy? > > See > http://lists.foresightlinux.org/pipermail/foresight-commits/2013-April/060814.html > > for details.
Typically, the answer has been "service httpd condrestart" but that's a problem; what we really want for httpd, is a new option "condgraceful" that does a graceful restart only if it is already running. (We do not want it to run at initial install time, for instance.) So, that points out one missing thing. Need to fall back to DIRECT if the local server can't be reached. ... António would like us to move to wsgi since it's what's being maintained actively upstream, which makes sense. It's not like the apache support is about to be deleted, but other than the regression fixes that we have seen lately (thanks!) we're unlikely to see much new happen there. Makes me wonder about invoking wsgi through xinetd. Looking for a few seconds at the gunicorn page doesn't make it immediately obvious that it has a one-shot mode. uWSGI can be run from xinetd but I don't know whether it will work with Conary; never tried. http://uwsgi-docs.readthedocs.org/en/latest/Inetd.html _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
