Customizing GNUmed client startup and shutdown
There are several hooks for customization of the startup/shutdown process built in. One can, of course, always write custom shell scripts/batch files to launch the client and/or hack the Python source code itself to achieve any needed behaviour.
Startup
command line
The GNUmed client accepts a few command line options. They are documented in the
man page. The options are passed to the
/usr/bin/gnumed
launcher shell script and eventually to the
gnumed.py
Python launcher script.
In particular, it may be convenient to use
--conf-file
to tell the GNUmed client to use a certain
configuration file.
gnumed launcher shell script
The client is usually launched with the
/usr/bin/gnumed
shell script which is included in the release tarball. This script looks for
-
/etc/gnumed/gnumed-startup-local.sh
- can be used for site-wide "local" customization
-
~/.gnumed/scripts/gnumed-startup-local.sh
- can be used for user-specific customization
and executes them (in that order) if they exist. Both scripts can do anything the user launching
/usr/bin/gnumed
can do (unless they are setuid-root). GNUmed as a project will never overwrite those files (but your package manager may decide to provide an updated
/etc/gnumed/gnumed-startup-local.sh
from time to time).
gnumed.py Python launcher script
When this script has been called the client as such is actually running. During startup two
hooks provide for customization:
- hook
startup-before-GUI
- this is called before the wxPython GUI is initialized
- hook
startup-post-GUI-init
- this is called after the wxPython GUI has been initialized before flow control is handed to user input
Shutdown
During shutdown the hook
shutdown-post-GUI
is called when the wxPython GUI has been closed.
|
Das Urheberrecht © liegt bei den mitwirkenden Autoren. Alle Inhalte dieser Kollaborations-Plattform sind Eigentum der Autoren. Ideen, Anfragen oder Probleme bezüglich TWiki? Feedback senden
|