From 1c54466ff7d6a2673453042164b8a14cf4fb577d Mon Sep 17 00:00:00 2001 From: Michael Fenn Date: Mon, 19 Aug 2013 19:30:16 -0400 Subject: Reporting: have bcfg2-report-collector be explicit about detaching Following the same logic as 360ba2e7, we should be explicit about the need to detach the bcfg2-report-collector process. Side note: this bit me because I was starting the bcfg2 server processes via SSH, and the way python-daemon checks for being started by inetd is to see if stdin is a socket. (??) --- src/lib/Bcfg2/Reporting/Collector.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/lib/Bcfg2') diff --git a/src/lib/Bcfg2/Reporting/Collector.py b/src/lib/Bcfg2/Reporting/Collector.py index 3d224432e..4556cda82 100644 --- a/src/lib/Bcfg2/Reporting/Collector.py +++ b/src/lib/Bcfg2/Reporting/Collector.py @@ -82,7 +82,7 @@ class ReportingCollector(object): """Startup the processing and go!""" self.terminate = threading.Event() atexit.register(self.shutdown) - self.context = daemon.DaemonContext() + self.context = daemon.DaemonContext(detach_process=True) if self.setup['daemon']: self.logger.debug("Daemonizing") -- cgit v1.2.3-1-g7c22