Question

I wrote a small Python application that runs as a daemon. It utilizes threading and queues.

I’m looking for general approaches to altering this application so that I can communicate with it while it’s running. Mostly I’d like to be able to monitor its health.

In a nutshell, I’d like to be able to do something like this:

python application.py start  # launches the daemon 

Later, I’d like to be able to come along and do something like:

python application.py check_queue_size  # return info from the daemonized process 

To be clear, I don’t have any problem implementing the Django-inspired syntax. What I don’t have any idea how to do is to send signals to the daemonized process (start), or how to write the daemon to handle and respond to such signals.

Like I said above, I’m looking for general approaches. The only one I can see right now is telling the daemon constantly log everything that might be needed to a file, but I hope there’s a less messy way to go about it.

UPDATE: Wow, a lot of great answers. Thanks so much. I think I’ll look at both Pyro and the web.py/Werkzeug approaches, since Twisted is a little more than I want to bite off at this point. The next conceptual challenge, I suppose, is how to go about talking to my worker threads without hanging them up.

Thanks again.

Answer 1

What about having it run an http server?

It seems crazy but running a simple web server for administrating your server requires just a few lines using web.py

You can also consider creating a unix pipe.