We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After the WSGI fix we are still seeing a handful of initialization log messages per restart of httpd:
After a restart at 10:45 a.m.:
01/24/2017 10:45:33:INFO :chapi:CH_SERVER: INITIALIZED CH_SERVER 01/24/2017 10:45:34:INFO :chapi:CH_SERVER: INITIALIZED CH_SERVER 01/24/2017 10:46:47:INFO :chapi:CH_SERVER: INITIALIZED CH_SERVER
Googling for "wsgi one time global initialization" found a response by Graham Dumpleton, the WSGI developer:
http://stackoverflow.com/questions/6221851/loading-a-file-just-once-on-initialization-of-python-script-using-mod-wsgi-and-b
Determine if this needs to be addressed. If it does need to be addressed, use mock-ch to experiment with solutions.
The text was updated successfully, but these errors were encountered:
This is fixed by:
Sorry, something went wrong.
tcmitchell
No branches or pull requests
After the WSGI fix we are still seeing a handful of initialization log messages per restart of httpd:
After a restart at 10:45 a.m.:
Googling for "wsgi one time global initialization" found a response by Graham Dumpleton, the WSGI developer:
http://stackoverflow.com/questions/6221851/loading-a-file-just-once-on-initialization-of-python-script-using-mod-wsgi-and-b
Determine if this needs to be addressed. If it does need to be addressed, use mock-ch to experiment with solutions.
The text was updated successfully, but these errors were encountered: