Chapter 15. Hiveconf
Folders are put into the configuration files by adding a path inside square brackets to the file as in the
following example:
[root@tlha-master conf.d]# cat vsmserver.hconf
#
# Hiveconf configuration file - VSM server
#
[/vsmserver]
unbind_ports_at_login=true
# Administrators email
admin_email = root@localhost
#
# Terminal servers. A list of hostnames. These will be used ...
# between the server and the agent. The names reported to ...
# the agent itself; names in terminalservers are not reported ...
#
terminalservers = tlagent-0.example.com
In this example, all three parameters ( unbind_ports_at_login , admin_email , and
terminalservers ) reside in the /vsmserver folder. This means that they should be addressed as
/vsmserver/unbind_ports_at_login , /vsmserver/admin_email and
/vsmserver/terminalservers respectively if used from inside a program using the Hivetool
libraries. This is of course not that important from the system administrator’s point of view, but it’s
important to understand the principle.
15.1.3. Mounting Datasources
One Hiveconf file can use another Hiveconf file by mounting the other file using a mount command as in
the following example:
%mount HA.hconf
The mount should be compared to a mount on a UNIX or Linux system. That is, the mount adds the tree
structure of the file mounted at exactly the place in the current tree structure where the mount command
was found.
Mounts can also use wildcards, as in the following example
%mount conf.d/
*
.hconf
The above is exactly what you’ll find if you look into the file /opt/thinlinc/etc/thinlinc.hconf.
Hiveconf will mount all files in /opt/thinlinc/etc/conf.d and add them to the current folder. This
is a very convenient way to add all configuration files for a specific software suite to the Hiveconf
namespace.
170
Comentarios a estos manuales