... that is flexible for use by a GUI later.


CURRENTLY
---------

This is the current way mousetrap is started and stopped.

```
$ mousetrap
... (status/debug output)
^C
... (ugly exception stuff)
$
```

Even after that, the user have to kill the mousetrap process.

```
$ ps aux | grep mousetrap
$ kill -9 12345
```

1. Users shouldn't have to deal with exceptions when performing a common operation like stopping mousetrap, unless there really is a problem.
2. Users shouldn't have to use kill to stop mousetrap.


PROPOSAL
--------

I recommend allowing MouseTrap to be controlled through the System V `service` command. For example

```
$ service mousetrap start
$ service mousetrap restart
$ service mousetrap stop
$ service mousetrap status
```

There are several advantages to this approach.

* Users, external applications, and MouseTrap itself can more easily start, restart (reload configuration), and stop MouseTrap.
* MouseTrap could be installed as a service to run on start up.
* External applications that know how to control applications through services can also control MouseTrap.
* MouseTrap itself could use this interface to control itself, including reloading configuration. This would provide an interface through which a GUI component (for example) could control MouseTrap.
* MouseTrap's design would improve because it would have to handle POSIX signals appropriately.
* The service script could be expanded to provide other functionality. E.g., a soft reload that would just reload the configuration, vs. a full reset which would reload the configuration and reset all components, etc.



INITIAL TO-DO LIST
------------------

1. Implement support for signals in existing MouseTrap application.
2. Implement a System V service script.
3. Make appropriate adjustments to setup.py and/or Makefile.am to install MouseTrap as a service.
4. Update README.md to reflect the new methods for controlling MouseTrap.