Beltane | ||
---|---|---|
<<< Previous | Next >>> |
With the Configure button in the upper left panel, you get access to the intaractive configuration (stored in $HOME/beltanerc The following functions are provided
The path to yules data directory (e.g. /var/lib/yule). This is the directory where client file signature databases and client configuration files reside.
The path to yules pid file (e.g. /var/run/yule.pid).
The path to yules HTML status file (e.g. /var/lib/yule/yule.html). This is a file written by the server providing basic status information for the server itself and for the clients known to the server.
The path to the beltane_cp helper application.
The path to the beltane_update helper application.
Your login name.
Your login password. If this is blank, the stored password will be kept (rather than set to blank). If exactly 32 chars, the input is assumed to be an MD5 hash already, otherwise the MD5 hash will be computed and stored.
(integer) display at most this number of messages (set to 0 to display all messages).
(seconds) terminate session after this much seconds.
(TRUE/FALSE) yule is configured to strip the domain part from client names.
![]() | NOTE |
---|---|
Beltane will need the the FQDN of clients in the client database (or the IP number, if clients are known to yule by IP number only). In particular, Beltane will not function properly if you have only the hostname in the client database, and yule is configured to strip the domain. See the Section called The Clients panel> for more information on the client database. |
(TRUE/FALSE) database is PostgreSQL rather than MySQL.
The name of the table in the SQL database (default: log).
The host where the SQL server runs (for UNIX socket: localhost if MySQL, blank if PostgreSQL).
The name of the SQL database (default: samhain).
The name of the SQL user.
The password of the SQL user.
Unsupported, leave to FALSE.
<<< Previous | Home | Next >>> |
Functions | Performance issues and scalability |