"Daemonizing" an application.
rosuav at gmail.com
Wed Feb 27 12:03:28 CET 2013
On Wed, Feb 27, 2013 at 9:52 PM, Gilles Lenfant
<gilles.lenfant at gmail.com> wrote:
> Sorry for the obscure title, but I can't make short to explain what I'm searching for. :)
> I made an app (kind of proxy) that works without UI within it's process. So far, so good.
> Now I need to change "live" some controls of this application, without stopping it.
> So my app will be split in two :
> * A control app (say "appctl") for a console UI
> * A daemon (or agent ?) that runs the core of the app (say "appd"), processing inputs and outputs
Daemonizing is a fairly specific operation (forking and disconnecting
from the console), which may well be a part of what you're asking for,
but on the other hand may be unnecessary (if, for instance, you let
your core app be invoked by Upstart directly).
What form of control do you need? With many apps of this nature, the
only control required is Unix signals - particularly SIGHUP, to say
"I've edited your config files, go reread them". Your front end might
do the editing, or you could even abolish the control app altogether
and simply edit the configs manually. But if you need more, you'll
need to work out how you want them to communicate with each other.
What platform or platforms do you need this to run on?
Regardless of your answers to the above, I would say that in all
probability *yes*, you will be able to do this with just Python and
the standard library. There are a lot of batteries included with
More information about the Python-list