This file is indexed.

/usr/share/doc/gnumed/user-manual/GmManualCustomizingBackendLogin.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
28
29
30
31
32
33
<h1><a name="Customizing_Backend_Login"></a> Customizing Backend Login </h1>
<p />
GNUmed reads backend information from its <a href="GmManualConfigFiles.html" class="twikiLink">configuration files</a> (such as <a href="http://cvs.savannah.gnu.org/viewvc/gnumed/gnumed/client/etc/gnumed/gnumed-client.conf.example?root=gnumed&amp;view=log" rel="nofollow" target="_top">this one</a>). The information is aggregated and merged from all the configuration files it can find. Options are loaded in order from system-wide to user-local configuration files. This way you can partially define profiles in separate configuration files or override options within more specific files.
<p />
There must be a list option <code>profiles</code> under the group <code>[backend]</code> in at least one of those. This option defines which profiles will be offered for selection in the login dialog. Example:
<pre>
&#91;backend]
profiles &#61; $profiles$
public GNUmed database
local GNUmed database
$profiles$
</pre>
This defines two backend profiles to select from in the login dialog. Each profile holds a collection of options defining how to access a particular backend. Example:
<pre>
&#91;profile public GNUmed database]
host &#61; publicdb.gnumed.de
port &#61; 5432
database &#61; gnumed&#95;v9
encoding &#61; UTF8
public/open access &#61; 1
help desk &#61; &#60;gnumed-devel&#64;gnu.org&#62;
</pre>
This defines the options for the backend profile <em>public GNUmed database</em> which is seen in the profile listing above.
<p /> <ul>
<li> to connect to localhost via UNIX domain sockets leave the option <code>host</code> empty
</li> <li> the <code>database</code> will have to be adjusted with most major releases <ul>
<li> usually this will be done by either your package maintainer or your local system administrator
</li> <li> for configuration files in a user home directory this may need to be done by the user
</li></ul> 
</li></ul> 
<hr />
<p />
<hr />