Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #18030
| From | Lie Ryan <lie.1296@gmail.com> |
|---|---|
| Subject | Re: Daemon management |
| Date | 2011-12-28 04:23 +1100 |
| References | <alpine.DEB.2.02.1112270226440.4050@pc7.dolda2000.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.4140.1325006608.27778.python-list@python.org> (permalink) |
On 12/27/2011 12:43 PM, Fredrik Tolf wrote: > Dear list, > > Lately, I've had a personal itch to scratch, in that I run a couple of > Python programs as daemons, and sometimes want to inspect or alter them > in ad-hoc ways, or other times need to do things to them that are less > ad-hoc in nature, but nevertheless lack a natural user interface. > > In order to solve that problem, I wrote a small library to allow the > daemon to simply listen to some socket and accept arbitrary, but easily > definable, commands. It also provides a "remote REPL" to allow me to run > arbitrary Python code interactively in the context of the daemon. > > I was actually a bit surprised that I couldn't find any obvious existing > solution to the problem, so I'm writing this message in order to share > mine, just in case anyone else would happen to have the same problem as > I had and doesn't want to reinvent the wheel yet again: This is possible through the use of a debugger. I've never used it, but I heard good thing of winpdb which has remote debugging. (http://winpdb.org/) Another tool that I've never used is rconsole, part of rfoo library, which appears to be similar to pdm; it is also intended for the same kind of problem, managing long-running-processes/daemons.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Daemon management Lie Ryan <lie.1296@gmail.com> - 2011-12-28 04:23 +1100
csiph-web