2.1. akira --- Network management application

2.1.1. Synopsis

akira [-c <config-file>] [-f] [-g] [-t <directory>] [-u <username>]

akira [-h | -V]

2.1.2. Description

akira is a network management application with a web-based user interface. It also implements a REST API interface that can be used by non-interactive clients.

To access akira's web-based user interface, users require a JavaScript-capable web browser that supports modern web standards.

2.1.3. Options

-c <config-file>: Use <config-file> as the akira configuration file. The default is /etc/akira/akira.conf.

-f: Don't daemonize the akira process. Run it in the foreground.

-g: Don't daemonize the akira process. Run it in the foreground. Force all logging to standard-error.

-h: Print program usage information and exit.

-t <directory>: chroot(2) to <directory> after processing the command line arguments, but before reading the configuration file.

Note

This option should be used in conjunction with the -u option, as chrooting a process running as root doesn't enhance security on most systems; the way chroot(2) is defined allows a process with root privileges to escape a chroot jail.

-u <username>

setuid(2) to user <username> after completing privileged operations, such as creating sockets that listen on privileged ports.

On Linux, akira uses the kernel's capability mechanism to drop all root privileges except the ability to bind(2) to a privileged port (CAP_NET_BIND_SERVICE) and set process resource limits (CAP_SYS_RESOURCE).

-V: Print program version and exit.

2.1.4. Files

/etc/akira/akira.conf

The default configuration file. A complete description of akira's configuration file is provided in akira.conf(5) and in the Akira User Manual.

/run/akira/akira.pid

The default process ID file.

2.1.5. See also

akira.conf(8)