==output==
jlh@dmt600u:~/Projects/tg$ cd foo/
jlh@dmt600u:~/Projects/tg/foo$ ./start-foo.py
/usr/lib/python2.4/site-packages/CherryPy-2.2.1-py2.4.egg/cherrypy/lib/profiler.py:54:
UserWarning: Your installation of Python doesn't have a profile
module. If you're on Debian, you can apt-get python2.4-profiler from
non-free in a separate step. See
http://www.cherrypy.org/wiki/ProfilingOnDebian for details.
warnings.warn(msg)
/usr/lib/python2.4/site-packages/CherryPy-2.2.1-py2.4.egg/cherrypy/lib/profiler.py:54:
UserWarning: Your installation of Python doesn't have a profile
module. If you're on Debian, you can apt-get python2.4-profiler from
non-free in a separate step. See
http://www.cherrypy.org/wiki/ProfilingOnDebian for details.
warnings.warn(msg)
2006-12-09 14:46:59,706 cherrypy.msg INFO CONFIG: Server parameters:
2006-12-09 14:46:59,707 cherrypy.msg INFO CONFIG:
server.environment: development
2006-12-09 14:46:59,707 cherrypy.msg INFO CONFIG: server.log_to_screen: True
2006-12-09 14:46:59,707 cherrypy.msg INFO CONFIG: server.log_file:
2006-12-09 14:46:59,707 cherrypy.msg INFO CONFIG: server.log_tracebacks: True
2006-12-09 14:46:59,708 cherrypy.msg INFO CONFIG:
server.log_request_headers: True
2006-12-09 14:46:59,708 cherrypy.msg INFO CONFIG:
server.protocol_version: HTTP/1.0
2006-12-09 14:46:59,708 cherrypy.msg INFO CONFIG: server.socket_host:
2006-12-09 14:46:59,708 cherrypy.msg INFO CONFIG: server.socket_port: 8080
2006-12-09 14:46:59,709 cherrypy.msg INFO CONFIG: server.socket_file:
2006-12-09 14:46:59,709 cherrypy.msg INFO CONFIG: server.reverse_dns: False
2006-12-09 14:46:59,709 cherrypy.msg INFO CONFIG: server.socket_queue_size: 5
2006-12-09 14:46:59,709 cherrypy.msg INFO CONFIG: server.thread_pool: 10
2006-12-09 14:46:59,941 cherrypy.msg INFO HTTP: Serving HTTP on
http://localhost:8080/
2006-12-09 14:47:10,497 cherrypy.msg INFO ENGINE: <Ctrl-C> hit:
shutting down autoreloader
2006-12-09 14:47:10,500 cherrypy.msg INFO ENGINE: <Ctrl-C> hit:
shutting down autoreloader
2006-12-09 14:47:10,501 cherrypy.msg INFO HTTP: HTTP Server shut down
2006-12-09 14:47:10,507 cherrypy.msg INFO HTTP: HTTP Server shut down
2006-12-09 14:47:10,534 cherrypy.msg INFO ENGINE: CherryPy shut down
2006-12-09 14:47:10,637 cherrypy.msg INFO ENGINE: CherryPy shut down
== end output ==
notice after the "INFO HTTP: Serving"... that messages are being
duplicated? It's been doing this ever since I started learning TG
(1.0b1) but I hadn't noticed until now (1.0b2)
I noticed when I was hooking in to call_on_startup/call_on_shutdown.
I had logging in my call back functions and those log messages were
duplicating. I couldn't find a reason that my code would be executed
twice so I created a new clean project et voila -- there is the same
thing in a clean project with no code from me.
Is this of concern?
Thanks,
Jeff
Cherrypy 2.2 runs two processes when in development mode when it's set
to reload. This is normal. This does not happen in production mode and
won't happen ever in CP3, which involved a reload rewrite.
Karl,
Thanks for the info -- I didn't see any negative effects outside of me
being confused by my duplicate log entries. I thought I had a logic
error in my code ;) Since I am new to TG I wanted to make sure that
I knew what was going on.
Thanks again,
Jeff