Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #40054

Re: "Daemonizing" an application.

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On 27 February 2013 11:03, Chris Angelico <rosuav@gmail.com> wrote:

> On Wed, Feb 27, 2013 at 9:52 PM, Gilles Lenfant
> <gilles.lenfant@gmail.com> wrote:
> > Hello,
> >
> > 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
> Python :)
>

One solution is to use XMLRPC to communicate with the daemonized process.
This does involve the daemon listening on the local network. The GUI can
then connect to the daemon and send it commands which essentially is
calling functions on the daemon. These can then change certain behaviors of
the daemon process without restarting it. If you want to be hardcore you
can use sockets. There are other networking libs like Twisted and RabbitMQ,
but they might be a bit overkill for your purpose.

But whether any of this is ok depends on your use case. The signals Chris
mentioned will also work. Alternatively there are a number of filewatching
libraries like watchdog or https://github.com/seb-m/pyinotify which you can
use to monitor changes to a config file if that's the way you want to go.

-- 
./Sven

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

"Daemonizing" an application. Gilles Lenfant <gilles.lenfant@gmail.com> - 2013-02-27 02:52 -0800
  Re: "Daemonizing" an application. Chris Angelico <rosuav@gmail.com> - 2013-02-27 22:03 +1100
  Re: "Daemonizing" an application. Werner Thie <werner@thieprojects.ch> - 2013-02-27 12:08 +0100
  Re: "Daemonizing" an application. Sven <svenito@gmail.com> - 2013-02-27 11:15 +0000
  Re: "Daemonizing" an application. Gilles Lenfant <gilles.lenfant@gmail.com> - 2013-02-27 05:06 -0800
    Re: "Daemonizing" an application. Chris Angelico <rosuav@gmail.com> - 2013-02-28 00:21 +1100
    Re: "Daemonizing" an application. "Vytas D." <vytasd2013@gmail.com> - 2013-02-27 13:46 +0000
  Re: "Daemonizing" an application. Tarek Ziadé <tarek@ziade.org> - 2013-02-27 14:55 +0100
    Re: "Daemonizing" an application. Gilles Lenfant <gilles.lenfant@gmail.com> - 2013-02-27 06:52 -0800
    Re: "Daemonizing" an application. Gilles Lenfant <gilles.lenfant@gmail.com> - 2013-02-27 06:52 -0800
  Re: "Daemonizing" an application. Tarek Ziadé <tarek@ziade.org> - 2013-02-27 15:00 +0100

csiph-web