Programs and files

LiveConfig Server

The LiveConfig server is usually installed at /usr/sbin/liveconfig. The following command line options are accepted:

--activate

activate a LiveConfig license, see License Activation

-c FILE, --config=FILE

use configuration file FILE, see Configuration

--db-check

check integrity of LiveConfig database

--diag

run some diagnostic/self-test functions (might be required for support requests)

-f, --foreground

run LiveConfig in foreground

-h, --help

show list of available command line arguments

--init

enter initialization code for onboarding (required only during initial installation)

--ip-blocked

show list of blocked IP addresses due to too many login attempts

--ip-unblock <IP>

unblock IP address <IP> immediately

-k <command>

control the LiveConfig process:

start

start LiveConfig

stop

immediately stop LiveConfig

reload

reload configuration

--pwreset

reset password for the admin account - see Password Initialization

--status, -s

show status of the running LiveConfig process

-v, --version

show version number of LiveConfig

Utilities

Some utilities are installed both with LiveConfig server and with LiveConfig client:

  • lcbackup to backup/restore webspace, e-mail and databases

  • lclogparse for realtime analysis of log files

  • lclogsplit for splitting and analysing web log files (access_log)

  • lclua, a Lua interpreter with LiveConfig extensions for developing and testing custom Lua scripts (see also Lua API)

  • lcpolicyd, a policy daemon to limit outgoing e-mails per user

  • lcsam, the SpamAssassin Milter, to integrate spam filter software

  • lcterm, a utility program required for shell access via web terminal

lcdbbackup

The program lcdbbackup enables the safe copying of SQLite databases. If the LiveConfig server is used with the integrated SQLite database, the database file (configuration option db_name, usually /var/lib/liveconfig/liveconfig.db) should be backed up regularly with lcdbbackup. This program ensures that the database copy created is consistent. With a “normal” copy, the database file can possibly be copied in an inconsistent state, the backup would be worthless then.

Usage: lcdbbackup <source file> <destination file>