/usr/share/doc/gnumed/user-manual/GmManualClientMaintenance.html is in gnumed-doc 1.1.7-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 | <h1><a name="Routine_Client_Maintenance_Tasks"></a> Routine Client Maintenance Tasks </h1>
<p />
<h3><a name="Disk_space"></a> Disk space </h3>
<p />
GNUmed uses scrap files for temporary local storage of patient data. In some cases it is, however, beyond the control of any particular GNUmed client when those files can be deleted. It is advisable to check the local temporary directories manually for deletable files from time to time. Those directories include:
<p /> <ul>
<li> <code>~/.gnumed/tmp/</code> (all files in this directory and its subdirectories can be deleted when there is no GNUmed client running under this user)
</li> <li> <code>~/.gnumed/backup/</code> (check for old backups not needed anymore)
</li> <li> <code>~/gnumed/logs/</code> (whenever an error occurs the log file is copied here)
</li> <li> <code>~/gnumed/export/</code> (subdirectories may contain files that was once used to post-process patient data exported from GNUmed)
</li> <li> <code>/tmp/gnumed/</code> <ul>
<li> subdirectories will contain files created specific to a particular client
</li> <li> clients will remove those files during shutdown if possible (unless started with <code>--debug</code>)
</li> <li> on reboot <code>/tmp/</code> will most likely be cleared of any remnants
</li></ul>
</li></ul>
<p />
<h3><a name="Keeping_the_client_up_to_date"></a> Keeping the client up-to-date </h3>
<p />
You should keep an eye on minor, bugfix, maintenance releases of whatever GNUmed major version you have installed. We strongly recommend keeping up with them. Installing minor releases will not require a database upgrade except under <em>very</em> rare circumstances (when a significant bug is discovered in the database).
<p />
You can configure the client to check for new releases at startup or invoke the update check manually from within the client.
<p />
Note that it may take a few days until a new version is packaged for your specific platform.
<hr />
<p />
<hr />
|