unbound-anchor

package: libunbound

title: unbound-anchor(8)

summary: Unbound 1.25.1 anchor utility.

text:
# unbound-anchor(8)

## NAME
unbound-anchor - Unbound 1.25.1 anchor utility.

## SYNOPSIS
unbound-anchor [opts]

## DESCRIPTION
unbound-anchor performs setup or update of the root trust anchor for DNSSEC validation. The program fetches the trust anchor with the method from RFC 7958 when regular RFC 5011 update fails to bring it up to date. It can be run from the commandline, or run as part of startup scripts before you start the unbound(8) DNS server.

Note that if you want to use RFC 5011 with Unbound (i.e., the auto-trust-anchor-file option) so that trust anchor information is automatically tracked by Unbound during operation, the user that Unbound runs under (by default 'unbound') must have write permissions to the file and the directory the file lives in (for creating temporary files). In this case you would probably want to run this program as the designated Unbound user.

Suggested usage:

```
# in the init scripts.
# provide or update the root anchor (if necessary)
unbound-anchor -a "/var/lib/unbound/root.key"
# Please note usage of this root anchor is at your own risk
# and under the terms of our LICENSE (see source).
#
# start validating resolver
# the unbound.conf contains:
# auto-trust-anchor-file: "/var/lib/unbound/root.key"
unbound -c unbound.conf
```

This tool provides builtin default contents for the root anchor and root update certificate files.

It tests if the root anchor file works, and if not, and an update is possible, attempts to update the root anchor using the root update certificate. It performs a https fetch of root-anchors.xml and checks the results (RFC 7958); if all checks are successful, it updates the root anchor file. Otherwise the root anchor file is unchanged. It performs RFC 5011 tracking if the DNSSEC information available via the DNS makes that possible.

It does not perform an update if the certificate is expired, if the network is down or other errors occur.

The available options are:

-a <file>

The root anchor key file, that is read in and written out. Default is /var/lib/unbound/root.key. If the file does not exist, or is empty, a builtin root key is written to it.

-c <file>

The root update certificate file, that is read in. Default is /var/lib/unbound/icannbundle.pem. If the file does not exist, or is empty, a builtin certificate is used.

-l

List the builtin root key and builtin root update certificate on stdout.

-u <name>

The server name, it connects to https://name. Specify without https:// prefix. The default is "data.iana.org". It connects to the port specified with -P. You can pass an IPv4 address or IPv6 address (no brackets) if you want.

-S

Do not use SNI for the HTTPS connection. Default is to use SNI.

-b <address>

The source address to bind to for domain resolution and contacting the server on https. May be either an IPv4 address or IPv6 address (no brackets).

-x <path>

The pathname to the root-anchors.xml file on the server. (forms URL with -u). The default is /root-anchors/root-anchors.xml.

-s <path>

The pathname to the root-anchors.p7s file on the server. (forms URL with -u). The default is /root-anchors/root-anchors.p7s. This file has to be a PKCS7 signature over the xml file, using the pem file (-c) as trust anchor.

-n <name>

The emailAddress for the Subject of the signer's certificate from the p7s signature file. Only signatures from this name are allowed. The default is dnssec@iana.org. If you pass "" then the emailAddress is not checked.

-4

Use IPv4 for domain resolution and contacting the server on https. Default is to use IPv4 and IPv6 where appropriate.

-6

Use IPv6 for domain resolution and contacting the server on https. Default is to use IPv4 and IPv6 where appropriate.

-f <resolv.conf>

Use the given resolv.conf file. Not enabled by default, but you could try to pass /etc/resolv.conf on some systems. It contains the IP addresses of the recursive nameservers to use. However, since this tool could be used to bootstrap that very recursive nameserver, it would not be useful (since that server is not up yet, since we are bootstrapping it). It could be useful in a situation where you know an upstream cache is deployed (and running) and in captive portal situations.

-r <root.hints>

Use the given root.hints file (same syntax as the BIND and Unbound root hints file) to bootstrap domain resolution. By default a list of builtin root hints is used. unbound-anchor goes to the network itself for these roots, to resolve the server (-u option) and to check the root DNSKEY records. It does so, because the tool when used for bootstrapping the recursive resolver, cannot use that recursive resolver itself because it is bootstrapping that server.

-R

Allow fallback from -f <resolv.conf> file to direct root servers query. It allows you to prefer local resolvers, but fallback automatically to direct root query if they do not respond or do not support DNSSEC.

-v

More verbose. Once prints informational messages, multiple times may enable large debug amounts (such as full certificates or byte-dumps of downloaded files). By default it prints almost nothing. It also prints nothing on errors by default; in that case the original root anchor file is simply left undisturbed, so that a recursive server can start right after it.

-C <unbound.conf>

Debug option to read <unbound.conf> into the resolver process used.

-P <port>

Set the port number to use for the https connection. The default is 443.

-F

Debug option to force update of the root anchor through downloading the xml file and verifying it with the certificate. By default it first tries to update by contacting the DNS, which uses much less bandwidth, is much faster (200 msec not 2 sec), and is nicer to the deployed infrastructure. With this option, it still attempts to do so (and may verbosely tell you), but then ignores the result and goes on to use the xml fallback method.

-h

Show the version and commandline option help.

## EXIT CODE
This tool exits with value 1 if the root anchor was updated using the certificate or if the builtin root-anchor was used. It exits with code 0 if no update was necessary, if the update was possible with RFC 5011 tracking, or if an error occurred.

You can check the exit value in this manner:

```
unbound-anchor -a "root.key" || logger "Please check root.key"
```

Or something more suitable for your operational environment.

## TRUST
The root keys and update certificate included in this tool are provided for convenience and under the terms of our license (see the LICENSE file in the source distribution or https://github.com/NLnetLabs/unbound/blob/master/LICENSE and might be stale or not suitable to your purpose.

By running unbound-anchor -l the keys and certificate that are configured in the code are printed for your convenience.

The built-in configuration can be overridden by providing a root-cert file and a rootkey file.

## FILES
/var/lib/unbound/root.key

The root anchor file, updated with 5011 tracking, and read and written to. The file is created if it does not exist.

/var/lib/unbound/icannbundle.pem

The trusted self-signed certificate that is used to verify the downloaded DNSSEC root trust anchor. You can update it by fetching it from https://data.iana.org/root-anchors/icannbundle.pem (and validate it). If the file does not exist or is empty, a builtin version is used.

https://data.iana.org/root-anchors/root-anchors.xml

Source for the root key information.

https://data.iana.org/root-anchors/root-anchors.p7s

Signature on the root key information.

## SEE ALSO
unbound.conf(5), unbound(8).

## AUTHOR
Unbound developers are mentioned in the CREDITS file in the distribution.

## COPYRIGHT
1999-2026, NLnet Labs


libvirtd

package: libvirt-daemon

title: libvirtd(8)

summary: libvirt management daemon

text:
# libvirtd(8)

## NAME
libvirtd - libvirt management daemon

## SYNOPSIS
libvirtd [OPTION]...

## DESCRIPTION
The libvirtd program is the server side daemon component of the libvirt virtualization management system.

This daemon runs on host servers and performs required management tasks for virtualized guests. This includes activities such as starting, stopping and migrating guests between host servers, configuring and manipulating networking, and managing storage for use by guests.

The libvirt client libraries and utilities connect to this daemon to issue tasks and collect information about the configuration and resources of the host system and guests.

By default, the libvirtd daemon listens for requests on a local Unix domain socket. Using the -l | --listen command line option, the libvirtd daemon can be instructed to additionally listen on a TCP/IP socket. The TCP/IP socket to use is defined in the libvirtd configuration file.

Restarting libvirtd does not impact running guests. Guests continue to operate and will be picked up automatically if their XML configuration has been defined. Any guests whose XML configuration has not been defined will be lost from the configuration.

## SYSTEM SOCKET ACTIVATION
The libvirtd daemon is capable of starting in two modes.

In the traditional mode, it will create and listen on UNIX sockets itself. If the --listen parameter is given, it will also listen on TCP/IP socket(s), according to the listen_tcp and listen_tls options in /etc/libvirt/libvirtd.conf

In socket activation mode, it will rely on systemd to create and listen on the UNIX, and optionally TCP/IP, sockets and pass them as pre-opened file descriptors. In this mode, it is not permitted to pass the --listen parameter, and most of the socket related config options in /etc/libvirt/libvirtd.conf will no longer have any effect. To enable TCP or TLS sockets use either

```
$ systemctl start libvirtd-tls.socket
```

Or

```
$ systemctl start libvirtd-tcp.socket
```

Socket activation mode is generally the default when running on a host OS that uses systemd. To revert to the traditional mode, all the socket unit files must be masked:

```
$ systemctl mask libvirtd.socket libvirtd-ro.socket \

   libvirtd-admin.socket libvirtd-tls.socket libvirtd-tcp.socket
```

On top of that make sure that the --timeout argument is not used for the daemon since it would not be started upon any later connection.

If using libvirt-guests service then the ordering for that service needs to be adapted so that it is ordered after the service unit instead of the socket unit. Since dependencies and ordering cannot be changed with drop-in overrides, the whole libvirt-guests unit file needs to be changed. In order to preserve such change copy the installed /usr/lib/systemd/system/libvirt-guests.service to /etc/systemd/system/libvirt-guests.service and make the change there, specifically make sure the After= ordering mentions libvirtd.service and not libvirtd.socket:

```
[Unit]
After=libvirtd.service
```

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-l, --listen

Listen for TCP/IP connections. This should not be set if using systemd socket activation. Instead activate the libvirtd-tls.socket or libvirtd-tcp.socket unit files.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are neither any client connections nor any running domains.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP libvirtd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/libvirtd.conf

The default configuration file used by libvirtd, unless overridden on the command line using the -f | --config option.

Depending on what driver is installed, then the following files are also read:

- /etc/libvirt/qemu.conf for the QEMU driver

- /etc/libvirt/lxc.conf for the LXC driver

- /etc/libvirt/libxl.conf for the libxl driver

These files contain various knobs and default values for virtual machines created within their respective drivers, and offer a way to override the built in defaults, for instance (but not limited to): paths to various supplementary binaries, TLS certificates location, graphical consoles configuration and others. Location of neither of these files can be overridden by any command line switch.

- /run/libvirt/libvirt-sock

- /run/libvirt/libvirt-sock-ro

The sockets libvirtd will use.

•

/etc/pki/CA/cacert.pem

The TLS Certificate Authority certificate libvirtd will use.

•

/etc/pki/libvirt/servercert.pem

The TLS Server certificate libvirtd will use.

•

/etc/pki/libvirt/private/serverkey.pem

The TLS Server private key libvirtd will use.

•

/run/libvirtd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/libvirtd.conf

The default configuration file used by libvirtd, unless overridden on the command line using the -f``|--config`` option.

If QEMU driver is installed, then the following file is also read:

•

$XDG_CONFIG_HOME/libvirt/qemu.conf

If the file exists, it can contain various knobs and default values for virtual machines created within QEMU driver, and offers a way to override the built in defaults, for instance (but not limited to): paths to various supplementary binaries, TLS certificates location, graphical consoles configuration and others. Location of this file can't be overridden by any command line switch.

•

$XDG_RUNTIME_DIR/libvirt/libvirt-sock

The socket libvirtd will use.

•

$HOME/.pki/libvirt/cacert.pem

The TLS Certificate Authority certificate libvirtd will use.

•

$HOME/.pki/libvirt/servercert.pem

The TLS Server certificate libvirtd will use.

•

$HOME/.pki/libvirt/serverkey.pem

The TLS Server private key libvirtd will use.

•

$XDG_RUNTIME_DIR/libvirt/libvirtd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, libvirtd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, libvirtd will use $HOME/.cache

## EXAMPLES
To retrieve the version of libvirtd:

```
# libvirtd --version
libvirtd (libvirt) 11.10.0
```

To start libvirtd, instructing it to daemonize and create a PID file:

```
# libvirtd -d
# ls -la /run/libvirtd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/libvirtd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2012 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
libvirtd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), virt-install(1), virt-xml-validate(1), virt-top(1), virt-df(1), https://libvirt.org/


libvirt-guests

package: libvirt-daemon-common

title: libvirt-guests(8)

summary: suspend/resume running libvirt guests

text:
# libvirt-guests(8)

## NAME
libvirt-guests - suspend/resume running libvirt guests

## SYNOPSIS
libvirt-guests COMMAND

## DESCRIPTION
libvirt-guests is a service that can be used to coordinate guest and host lifecycle actions. By default, libvirt-guests will suspend running guests when the host shuts down, and restore them to their pre-shutdown state when the host reboots.

libvirt-guests is typically under control of systemd. When libvirt-guests.service is enabled, systemd will call libvirt-guests with the start COMMAND when the host boots. Conversely, systemd will call libvirt-guests with the stop COMMAND when the host shuts down.

libvirt-guests can be used directly. In addition to the start and stop COMMANDs, it also supports status, restart, condrestart, try-restart, reload, force-reload, gueststatus, and shutdown COMMANDs.

## FILES
libvirt-guests defines several variables to control service behavior. The default value of these variables can be overridden in:

•

/etc/sysconfig/libvirt-guests

The following variables are supported:

- URIS=default URIs to check for running guests. Example: URIS='default xen:///system xen+tcp://host/system lxc:///system'

- ON_BOOT=start Action taken on host boot

- start All guests which were running on shutdown are started on boot regardless of their autostart settings

- ignore libvirt-guests won't start any guest on boot, however, guests marked as autostart will still be automatically started by libvirtd

- START_DELAY=0 Number of seconds to wait between each guest start. Set to 0 to allow parallel startup.

- ON_SHUTDOWN=suspend Action taken on host shutdown

- suspend All running guests are suspended using virsh managedsave

- shutdown All running guests are asked to shutdown. Please be careful with this settings since there is no way to distinguish between a guest which is stuck or ignores shutdown requests and a guest which just needs a long time to shutdown. When setting ON_SHUTDOWN=shutdown, you must also set SHUTDOWN_TIMEOUT to a value suitable for your guests.

- PARALLEL_SHUTDOWN=0 Number of guests will be shutdown concurrently, taking effect when "ON_SHUTDOWN" is set to "shutdown". If Set to 0, guests will be shutdown one after another. Number of guests on shutdown at any time will not exceed number set in this variable.

- SHUTDOWN_TIMEOUT=300 Number of seconds we're willing to wait for a guest to shut down. If parallel shutdown is enabled, this timeout applies as a timeout for shutting down all guests on a single URI defined in the variable URIS. If this is 0, then there is no time out (use with caution, as guests might not respond to a shutdown request). The default value is 300 seconds (5 minutes).

- BYPASS_CACHE=0 If non-zero, try to bypass the file system cache when saving and restoring guests, even though this may give slower operation for some file systems.

- SYNC_TIME=0 If non-zero, try to sync guest time on domain resume. Be aware, that this requires guest agent with support for time synchronization running in the guest. By default, this functionality is turned off.

- PERSISTENT_ONLY=default Defines what type of guest virtual machine ON_SHUTDOWN action is applied to

- default This implements the already existing default behavior. If ON_SHUTDOWN action is shutdown, transient and persistent guest virtual machines are asked to shutdown. If ON_SHUTDOWN action is suspend, only persistent guest virtual machines are asked to suspend.

- true ON_SHUTDOWN action is executed only on persistent guest virtual machines. Transient guest virtual machines are not affected.

- false ON_SHUTDOWN action is executed on persistent and transient guest virtual machines.

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## LICENSE
libvirt-guests is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
libvirtd(8), https://libvirt.org/


virt-ssh-helper

title: virt-ssh-helper(8)

summary: libvirt socket proxy

text:
# virt-ssh-helper(8)

## NAME
virt-ssh-helper - libvirt socket proxy

## SYNOPSIS
virt-ssh-helper [OPTION]... URI

## DESCRIPTION
virt-ssh-helper is an internal tool used to handle connections coming from remote clients, and it's not intended to be called directly by the user.

## OPTIONS
URI

Local libvirt URI to connect the remote client to.

-r, --readonly

Make the connection read-only.

-h, --help

Display command line help usage then exit.

-V, --version

Display version information then exit.

## EXIT STATUS
The exit status will be zero on success, non-zero on failure.

## AUTHOR
Daniel P. Berrangé

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## COPYRIGHT
Copyright (C) 2020 Red Hat, Inc.

## LICENSE
virt-ssh-helper is distributed under the terms of the GNU LGPL v2+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

## SEE ALSO
virsh(1), https://libvirt.org/


virtinterfaced

package: libvirt-daemon-driver-interface

title: virtinterfaced(8)

text:
# virtinterfaced(8)

## NAME
virtinterfaced - libvirt host network interface management daemon

## SYNOPSIS
virtinterfaced [OPTION]...

## DESCRIPTION
The virtinterfaced program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts to provide management for host network interfaces.

The virtinterfaced daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtinterfaced does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup. None the less it is recommended to avoid restarting with running guests whenever practical.

## DAEMON STARTUP MODES
The virtinterfaced daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtinterfaced.conf will no longer have any effect.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtinterfaced will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtinterfaced.conf

The default configuration file used by virtinterfaced, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtinterfaced-sock

- /run/libvirt/virtinterfaced-sock-ro

- /run/libvirt/virtinterfaced-admin-sock

The sockets virtinterfaced will use.

The TLS Server private key virtinterfaced will use.

•

/run/virtinterfaced.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtinterfaced.conf

The default configuration file used by virtinterfaced, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtinterfaced-sock

- $XDG_RUNTIME_DIR/libvirt/virtinterfaced-admin-sock

The sockets virtinterfaced will use.

•

$XDG_RUNTIME_DIR/libvirt/virtinterfaced.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtinterfaced will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtinterfaced will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtinterfaced:

```
# virtinterfaced --version
virtinterfaced (libvirt) 11.10.0
```

To start virtinterfaced, instructing it to daemonize and create a PID file:

```
# virtinterfaced -d
# ls -la /run/virtinterfaced.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtinterfaced.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtinterfaced is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html,


virtlxcd

package: libvirt-daemon-driver-lxc

title: virtlxcd(8)

summary: libvirt LXC management daemon

text:
# virtlxcd(8)

## NAME
virtlxcd - libvirt LXC management daemon

## SYNOPSIS
virtlxcd [OPTION]...

## DESCRIPTION
The virtlxcd program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts to provide management for LXC containers.

The virtlxcd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtlxcd does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup. None the less it is recommended to avoid restarting with running guests whenever practical.

## DAEMON STARTUP MODES
The virtlxcd daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtlxcd.conf will no longer have any effect.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are neither any client connections nor any running domains.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtlxcd will reload its configuration.

## FILES
The virtlxcd program must be ran as root. Trying to start the program under a different user results in error.

•

/etc/libvirt/virtlxcd.conf

The default configuration file used by virtlxcd, unless overridden on the command line using the -f | --config option.

In addition to the default configuration file, virtlxcd reads configuration for the LXC driver from:

•

/etc/libvirt/lxc.conf

This file contains various knobs and default values for virtual machines created within LXC driver, and offers a way to override the built in defaults, Location of this file can't be overridden by any command line switch.

- /run/libvirt/virtlxcd-sock

- /run/libvirt/virtlxcd-sock-ro

- /run/libvirt/virtlxcd-admin-sock

The sockets virtlxcd will use.

The TLS Server private key virtlxcd will use.

•

/run/virtlxcd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

## EXAMPLES
To retrieve the version of virtlxcd:

```
# virtlxcd --version
virtlxcd (libvirt) 11.10.0
```

To start virtlxcd, instructing it to daemonize and create a PID file:

```
# virtlxcd -d
# ls -la /run/virtlxcd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtlxcd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtlxcd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html, https://libvirt.org/drvlxc.html


virtnetworkd

package: libvirt-daemon-driver-network

title: virtnetworkd(8)

text:
# virtnetworkd(8)

## NAME
virtnetworkd - libvirt virtual network management daemon

## SYNOPSIS
virtnetworkd [OPTION]...

## DESCRIPTION
The virtnetworkd program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts to provide management for virtual networks.

The virtnetworkd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtnetworkd does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup. None the less it is recommended to avoid restarting with running guests whenever practical.

## DAEMON STARTUP MODES
The virtnetworkd daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtnetworkd.conf will no longer have any effect.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtnetworkd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtnetworkd.conf

The default configuration file used by virtnetworkd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtnetworkd-sock

- /run/libvirt/virtnetworkd-sock-ro

- /run/libvirt/virtnetworkd-admin-sock

The sockets virtnetworkd will use.

The TLS Server private key virtnetworkd will use.

•

/run/virtnetworkd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtnetworkd.conf

The default configuration file used by virtnetworkd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtnetworkd-sock

- $XDG_RUNTIME_DIR/libvirt/virtnetworkd-admin-sock

The sockets virtnetworkd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtnetworkd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtnetworkd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtnetworkd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtnetworkd:

```
# virtnetworkd --version
virtnetworkd (libvirt) 11.10.0
```

To start virtnetworkd, instructing it to daemonize and create a PID file:

```
# virtnetworkd -d
# ls -la /run/virtnetworkd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtnetworkd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtnetworkd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html,


virtnodedevd

package: libvirt-daemon-driver-nodedev

title: virtnodedevd(8)

summary: libvirt host device management daemon

text:
# virtnodedevd(8)

## NAME
virtnodedevd - libvirt host device management daemon

## SYNOPSIS
virtnodedevd [OPTION]...

## DESCRIPTION
The virtnodedevd program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts to provide management for host devices.

The virtnodedevd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtnodedevd does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup. None the less it is recommended to avoid restarting with running guests whenever practical.

## DAEMON STARTUP MODES
The virtnodedevd daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtnodedevd.conf will no longer have any effect.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtnodedevd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtnodedevd.conf

The default configuration file used by virtnodedevd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtnodedevd-sock

- /run/libvirt/virtnodedevd-sock-ro

- /run/libvirt/virtnodedevd-admin-sock

The sockets virtnodedevd will use.

The TLS Server private key virtnodedevd will use.

•

/run/virtnodedevd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtnodedevd.conf

The default configuration file used by virtnodedevd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtnodedevd-sock

- $XDG_RUNTIME_DIR/libvirt/virtnodedevd-admin-sock

The sockets virtnodedevd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtnodedevd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtnodedevd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtnodedevd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtnodedevd:

```
# virtnodedevd --version
virtnodedevd (libvirt) 11.10.0
```

To start virtnodedevd, instructing it to daemonize and create a PID file:

```
# virtnodedevd -d
# ls -la /run/virtnodedevd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtnodedevd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtnodedevd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html, https://libvirt.org/drvnodedev.html


virtnwfilterd

package: libvirt-daemon-driver-nwfilter

title: virtnwfilterd(8)

text:
# virtnwfilterd(8)

## NAME
virtnwfilterd - libvirt network filter management daemon

## SYNOPSIS
virtnwfilterd [OPTION]...

## DESCRIPTION
The virtnwfilterd program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts to provide management for network filters.

The virtnwfilterd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtnwfilterd does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup. None the less it is recommended to avoid restarting with running guests whenever practical.

## DAEMON STARTUP MODES
The virtnwfilterd daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtnwfilterd.conf will no longer have any effect.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtnwfilterd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtnwfilterd.conf

The default configuration file used by virtnwfilterd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtnwfilterd-sock

- /run/libvirt/virtnwfilterd-sock-ro

- /run/libvirt/virtnwfilterd-admin-sock

The sockets virtnwfilterd will use.

The TLS Server private key virtnwfilterd will use.

•

/run/virtnwfilterd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtnwfilterd.conf

The default configuration file used by virtnwfilterd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtnwfilterd-sock

- $XDG_RUNTIME_DIR/libvirt/virtnwfilterd-admin-sock

The sockets virtnwfilterd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtnwfilterd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtnwfilterd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtnwfilterd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtnwfilterd:

```
# virtnwfilterd --version
virtnwfilterd (libvirt) 11.10.0
```

To start virtnwfilterd, instructing it to daemonize and create a PID file:

```
# virtnwfilterd -d
# ls -la /run/virtnwfilterd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtnwfilterd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtnwfilterd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html,


virtqemud

package: libvirt-daemon-driver-qemu

title: virtqemud(8)

summary: libvirt QEMU management daemon

text:
# virtqemud(8)

## NAME
virtqemud - libvirt QEMU management daemon

## SYNOPSIS
virtqemud [OPTION]...

## DESCRIPTION
The virtqemud program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts to provide management for QEMU virtual machines.

The virtqemud daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtqemud does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup. None the less it is recommended to avoid restarting with running guests whenever practical.

## DAEMON STARTUP MODES
The virtqemud daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtqemud.conf will no longer have any effect.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are neither any client connections nor any running domains.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtqemud will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtqemud.conf

The default configuration file used by virtqemud, unless overridden on the command line using the -f | --config option.

In addition to the default configuration file, virtqemud reads configuration for the QEMU driver from:

•

/etc/libvirt/qemu.conf

This file contains various knobs and default values for virtual machines created within QEMU driver, and offers a way to override the built in defaults, for instance (but not limited to): paths to various supplementary binaries, TLS certificates location, graphical consoles configuration and others. Location of this file can't be overridden by any command line switch.

- /run/libvirt/virtqemud-sock

- /run/libvirt/virtqemud-sock-ro

- /run/libvirt/virtqemud-admin-sock

The sockets virtqemud will use.

The TLS Server private key virtqemud will use.

•

/run/virtqemud.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtqemud.conf

The default configuration file used by virtqemud, unless overridden on the command line using the -f``|--config`` option.

In addition to the default configuration file, virtqemud reads configuration for the qemu driver from:

•

$XDG_CONFIG_HOME/libvirt/qemu.conf

If the file exists, it can contain various knobs and default values for virtual machines created within QEMU driver, and offers a way to override the built in defaults, for instance (but not limited to): paths to various supplementary binaries, TLS certificates location, graphical consoles configuration and others. Location of this file can't be overridden by any command line switch.

- $XDG_RUNTIME_DIR/libvirt/virtqemud-sock

- $XDG_RUNTIME_DIR/libvirt/virtqemud-admin-sock

The sockets virtqemud will use.

•

$XDG_RUNTIME_DIR/libvirt/virtqemud.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtqemud will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtqemud will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtqemud:

```
# virtqemud --version
virtqemud (libvirt) 11.10.0
```

To start virtqemud, instructing it to daemonize and create a PID file:

```
# virtqemud -d
# ls -la /run/virtqemud.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtqemud.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtqemud is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html, https://libvirt.org/drvqemu.html


virtsecretd

package: libvirt-daemon-driver-secret

title: virtsecretd(8)

summary: libvirt secret data management daemon

text:
# virtsecretd(8)

## NAME
virtsecretd - libvirt secret data management daemon

## SYNOPSIS
virtsecretd [OPTION]...

## DESCRIPTION
The virtsecretd program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts to provide management for secret data.

The virtsecretd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtsecretd does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup. None the less it is recommended to avoid restarting with running guests whenever practical.

## DAEMON STARTUP MODES
The virtsecretd daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtsecretd.conf will no longer have any effect.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are neither any client connections nor any ephemeral secrets.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtsecretd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtsecretd.conf

The default configuration file used by virtsecretd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtsecretd-sock

- /run/libvirt/virtsecretd-sock-ro

- /run/libvirt/virtsecretd-admin-sock

The sockets virtsecretd will use.

The TLS Server private key virtsecretd will use.

•

/run/virtsecretd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtsecretd.conf

The default configuration file used by virtsecretd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtsecretd-sock

- $XDG_RUNTIME_DIR/libvirt/virtsecretd-admin-sock

The sockets virtsecretd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtsecretd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtsecretd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtsecretd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtsecretd:

```
# virtsecretd --version
virtsecretd (libvirt) 11.10.0
```

To start virtsecretd, instructing it to daemonize and create a PID file:

```
# virtsecretd -d
# ls -la /run/virtsecretd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtsecretd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtsecretd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html, https://libvirt.org/drvsecret.html


virtstoraged

package: libvirt-daemon-driver-storage-core

title: virtstoraged(8)

summary: libvirt storage pool management daemon

text:
# virtstoraged(8)

## NAME
virtstoraged - libvirt storage pool management daemon

## SYNOPSIS
virtstoraged [OPTION]...

## DESCRIPTION
The virtstoraged program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts to provide management for storage pools.

The virtstoraged daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtstoraged does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup. None the less it is recommended to avoid restarting with running guests whenever practical.

## DAEMON STARTUP MODES
The virtstoraged daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtstoraged.conf will no longer have any effect.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtstoraged will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtstoraged.conf

The default configuration file used by virtstoraged, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtstoraged-sock

- /run/libvirt/virtstoraged-sock-ro

- /run/libvirt/virtstoraged-admin-sock

The sockets virtstoraged will use.

The TLS Server private key virtstoraged will use.

•

/run/virtstoraged.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtstoraged.conf

The default configuration file used by virtstoraged, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtstoraged-sock

- $XDG_RUNTIME_DIR/libvirt/virtstoraged-admin-sock

The sockets virtstoraged will use.

•

$XDG_RUNTIME_DIR/libvirt/virtstoraged.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtstoraged will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtstoraged will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtstoraged:

```
# virtstoraged --version
virtstoraged (libvirt) 11.10.0
```

To start virtstoraged, instructing it to daemonize and create a PID file:

```
# virtstoraged -d
# ls -la /run/virtstoraged.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtstoraged.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtstoraged is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html, https://libvirt.org/storage.html


virtvboxd

package: libvirt-daemon-driver-vbox

title: virtvboxd(8)

summary: libvirt VirtualBox management daemon

text:
# virtvboxd(8)

## NAME
virtvboxd - libvirt VirtualBox management daemon

## SYNOPSIS
virtvboxd [OPTION]...

## DESCRIPTION
The virtvboxd program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts to provide management for VirtualBox virtual machines.

The virtvboxd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtvboxd does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup.

## DAEMON STARTUP MODES
The virtvboxd daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtvboxd.conf will no longer have any effect.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtvboxd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtvboxd.conf

The default configuration file used by virtvboxd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtvboxd-sock

- /run/libvirt/virtvboxd-sock-ro

- /run/libvirt/virtvboxd-admin-sock

The sockets virtvboxd will use.

The TLS Server private key virtvboxd will use.

•

/run/virtvboxd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtvboxd.conf

The default configuration file used by virtvboxd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtvboxd-sock

- $XDG_RUNTIME_DIR/libvirt/virtvboxd-admin-sock

The sockets virtvboxd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtvboxd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtvboxd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtvboxd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtvboxd:

```
# virtvboxd --version
virtvboxd (libvirt) 11.10.0
```

To start virtvboxd, instructing it to daemonize and create a PID file:

```
# virtvboxd -d
# ls -la /run/virtvboxd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtvboxd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtvboxd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html, https://libvirt.org/drvvbox.html


virtlockd

package: libvirt-daemon-lock

title: virtlockd(8)

summary: libvirt lock management daemon

text:
# virtlockd(8)

## NAME
virtlockd - libvirt lock management daemon

## SYNOPSIS
virtlockd [OPTION]...

## DESCRIPTION
The virtlockd program is a server side daemon component of the libvirt virtualization management system that is used to manage locks held against virtual machine resources, such as their disks.

This daemon is not used directly by libvirt client applications, rather it is called on their behalf by libvirtd. By maintaining the locks in a standalone daemon, the main libvirtd daemon can be restarted without risk of losing locks. The virtlockd daemon has the ability to re-exec() itself upon receiving SIGUSR1, to allow live upgrades without downtime.

The virtlockd daemon listens for requests on a local Unix domain socket.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon and write PID file.

-f, --config FILE

Use this configuration file, overriding the default value.

-t, --timeout SECONDS

Automatically shutdown after SECONDS have elapsed with no active client or lock.

-p, --pid-file FILE

Use this name for the PID file, overriding the default value.

-v, --verbose

Enable output of verbose messages.

-V, --version

Display version information then exit.

## SIGNALS
On receipt of SIGUSR1, virtlockd will re-exec() its binary, while maintaining all current locks and clients. This allows for live upgrades of the virtlockd service.

## FILES

### When run as root
•

/etc/libvirt/virtlockd.conf

The default configuration file used by virtlockd, unless overridden on the command line using the -f | --config option.

•

/run/libvirt/virtlockd-sock

The sockets virtlockd will use.

•

/run/virtlockd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtlockd.conf

The default configuration file used by virtlockd, unless overridden on the command line using the -f | --config option.

•

$XDG_RUNTIME_DIR/libvirt/virtlockd-sock

The socket virtlockd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtlockd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

If $XDG_CONFIG_HOME is not set in your environment, virtlockd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtlockd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtlockd:

```
# virtlockd --version
virtlockd (libvirt) 11.10.0
```

To start virtlockd, instructing it to daemonize and create a PID file:

```
# virtlockd -d
# ls -la /run/virtlockd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtlockd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2013 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtlockd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
libvirtd(8), https://libvirt.org/


virtlogd

package: libvirt-daemon-log

title: virtlogd(8)

summary: libvirt log management daemon

text:
# virtlogd(8)

## NAME
virtlogd - libvirt log management daemon

## SYNOPSIS
virtlogd [OPTION]...

## DESCRIPTION
The virtlogd program is a server side daemon component of the libvirt virtualization management system that is used to manage logs from virtual machine consoles.

This daemon is not used directly by libvirt client applications, rather it is called on their behalf by libvirtd. By maintaining the logs in a standalone daemon, the main libvirtd daemon can be restarted without risk of losing logs. The virtlogd daemon has the ability to re-exec() itself upon receiving SIGUSR1, to allow live upgrades without downtime.

The virtlogd daemon listens for requests on a local Unix domain socket.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon and write PID file.

-f, --config FILE

Use this configuration file, overriding the default value.

-t, --timeout SECONDS

Automatically shutdown after SECONDS have elapsed with no active console log.

-p, --pid-file FILE

Use this name for the PID file, overriding the default value.

-v, --verbose

Enable output of verbose messages.

-V, --version

Display version information then exit.

## SIGNALS
On receipt of SIGUSR1, virtlogd will re-exec() its binary, while maintaining all current logs and clients. This allows for live upgrades of the virtlogd service.

## FILES

### When run as root
•

/etc/libvirt/virtlogd.conf

The default configuration file used by virtlogd, unless overridden on the command line using the -f | --config option.

•

/run/libvirt/virtlogd-sock

The sockets virtlogd will use.

•

/run/virtlogd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtlogd.conf

The default configuration file used by virtlogd, unless overridden on the command line using the -f | --config option.

•

$XDG_RUNTIME_DIR/libvirt/virtlogd-sock

The socket virtlogd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtlogd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

If $XDG_CONFIG_HOME is not set in your environment, virtlogd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtlogd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtlogd:

```
# virtlogd --version
virtlogd (libvirt) 11.10.0
```

To start virtlogd, instructing it to daemonize and create a PID file:

```
# virtlogd -d
# ls -la /run/virtlogd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtlogd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2015 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtlogd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
libvirtd(8), https://libvirt.org/


virt-sanlock-cleanup

package: libvirt-daemon-plugin-sanlock

title: virt-sanlock-cleanup(8)

text:
# virt-sanlock-cleanup(8)

## NAME
virt-sanlock-cleanup - remove stale sanlock resource lease files

## SYNOPSIS
virt-sanlock-cleanup

## DESCRIPTION
This tool removes any resource lease files created by the sanlock lock manager plugin. The resource lease files only need to exist on disks when a guest using the resource is active. This script reclaims the disk space used by resources which are not currently active.

## EXIT STATUS
Upon successful processing of leases cleanup, an exit status of 0 will be set. Upon fatal error a non-zero status will be set.

## AUTHOR
Daniel P. Berrangé

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## COPYRIGHT
Copyright (C) 2011, 2013 Red Hat, Inc.

## LICENSE
virt-sanlock-cleanup is distributed under the terms of the GNU GPL v2+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), online instructions, https://libvirt.org/


virtproxyd

package: libvirt-daemon-proxy

title: virtproxyd(8)

summary: libvirt proxy daemon

text:
# virtproxyd(8)

## NAME
virtproxyd - libvirt proxy daemon

## SYNOPSIS
virtproxyd [OPTION]...

## DESCRIPTION
The virtproxyd program is a server side daemon component of the libvirt virtualization management system.

It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.

This daemon runs on virtualization hosts and

- Listens on a UNIX socket to provide backwards compatibility for clients that previously connected to the libvirtd socket.

- Optionally listens on TCP ports for connections from off-node clients

Upon receiving RPC messages from a client virtproxyd will transparently forward them on to the appropriate modular daemon, and similarly relay back any asynchronous events.

By default, the virtproxyd daemon listens for requests on a local Unix domain socket with the same path previously used by libvirtd. The configuration file can be used to instruct it to also listen on TCP socket(s). Systemd socket activation is also supported to allow it to receive pre-opened listener sockets on startup.

Since virtproxyd merely forwards RPC messages, it has no important state, and can be restarted at any time. Clients should expect to reconnect after the restart.

## DAEMON STARTUP MODES
The virtproxyd daemon is capable of starting in two modes.

### Socket activation mode
On hosts with systemd it is started in socket activation mode and it will rely on systemd to create and listen on the UNIX, and optionally TCP/IP, sockets and pass them as pre-opened file descriptors. In this mode most of the socket related config options in /etc/libvirt/virtproxyd.conf will no longer have any effect. To enable TCP or TLS sockets use either

```
$ systemctl start virtproxyd-tls.socket
```

Or

```
$ systemctl start virtproxyd-tcp.socket
```

Note: The TCP socket uses plain unencrypted TCP connection and thus is insecure and should not be used.

### Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself. It will also listen on TCP/IP socket(s), according to the listen_tcp and listen_tls options in /etc/libvirt/virtproxyd.conf

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon & write PID file.

-f, --config *FILE*

Use this configuration file, overriding the default value.

-p, --pid-file *FILE*

Use this name for the PID file, overriding the default value.

-t, --timeout *SECONDS*

Exit after timeout period (in seconds), provided there are no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtproxyd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtproxyd.conf

The default configuration file used by virtproxyd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/libvirt-sock

- /run/libvirt/libvirt-sock-ro

The sockets virtproxyd will use.

•

/etc/pki/CA/cacert.pem

The TLS Certificate Authority certificate virtproxyd will use.

•

/etc/pki/libvirt/servercert.pem

The TLS Server certificate virtproxyd will use.

•

/etc/pki/libvirt/private/serverkey.pem

The TLS Server private key virtproxyd will use.

•

/run/virtproxyd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtproxyd.conf

The default configuration file used by virtproxyd, unless overridden on the command line using the -f``|--config`` option.

•

$XDG_RUNTIME_DIR/libvirt/libvirt-sock

The socket virtproxyd will use.

•

$HOME/.pki/libvirt/cacert.pem

The TLS Certificate Authority certificate virtproxyd will use.

•

$HOME/.pki/libvirt/servercert.pem

The TLS Server certificate virtproxyd will use.

•

$HOME/.pki/libvirt/serverkey.pem

The TLS Server private key virtproxyd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtproxyd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtproxyd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtproxyd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtproxyd:

```
# virtproxyd --version
virtproxyd (libvirt) 11.10.0
```

To start virtproxyd, instructing it to daemonize and create a PID file:

```
# virtproxyd -d
# ls -la /run/virtproxyd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtproxyd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtproxyd is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

## SEE ALSO
virsh(1), libvirtd(8), https://libvirt.org/daemons.html,


libvirt-dbus

package: libvirt-dbus

title: libvirt-dbus(8)

summary: D-Bus daemon exporting libvirt API

text:
# libvirt-dbus(8)

## NAME
libvirt-dbus - D-Bus daemon exporting libvirt API

## SYNOPSIS
libvirt-dbus [OPTION]...

## DESCRIPTION
libvirt-dbus wraps libvirt API to provide a high-level object-oriented API better suited for dbus-based applications.

Normally libvirt-dbus is started by D-Bus daemon on demand.

## OPTIONS
-h --help

Display command line help usage then exit.

--system

Connect to the system bus.

--session

Connect to the session bus.

-t --threads NUM

Configure maximal number of worker threads.

## BUGS
Please report all bugs you discover. This should be done via either:

a.

the mailing list

https://libvirt.org/contact.html

b.

the bug tracker

https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distribution / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt-dbus.

## LICENSE
libvirt-dbus is Free Software and licenced under LGPLv2+.

## SEE ALSO
https://libvirt.org/dbus.html, https://libvirt.org/


lighttpd

package: lighttpd

title: lighttpd(8)

summary: a fast, secure and flexible web server

text:
# lighttpd(8)

## NAME
lighttpd - a fast, secure and flexible web server

## SYNOPSIS
lighttpd [-ptDvVh] -f configfile [-m moduledir]

## DESCRIPTION
lighttpd (pronounced 'lighty') is an advanced HTTP daemon that aims to be secure, fast, compliant and very flexible. It has been optimized for high performance. Its feature set includes, but is not limited to, FastCGI, CGI, basic and digest HTTP authentication, output compression, URL rewriting.

This manual page only lists the command line arguments. For details on how to configure lighttpd and its modules see the files in the doc-directory.

## OPTIONS
The following options are supported:

-f configfile

Load configuration file configfile. Optionally, use -f - to read config from stdin; -f - is incompatible with -1.

-m moduledir

Use moduledir as the directory that contains modules, instead of the default.

-p

Print the parsed configuration file in its internal form and exit.

-t

Test the configuration file for syntax errors and exit.

-tt

Test the configuration file for syntax errors, load and initialize modules, and exit.

-D

Do not daemonize (go into background). The default is to daemonize.

-i secs

Trigger daemon graceful shutdown after secs of inactivity.

-1

Process single (one) request on stdin socket, then exit.

-v

Show version and exit.

-V

Show compile-time features and exit.

-h

Show a brief help message and exit.

## FILES
/etc/lighttpd/lighttpd.conf

The standard location for the configuration file.

/run/lighttpd.pid

The standard location for the PID of the running lighttpd process.

## SEE ALSO
Online Documentation: https://wiki.lighttpd.net/

spawn-fcgi(1)

Hypertext Transfer Protocol -- HTTP/1.1, RFC 2616.

HTTP Authentication: Basic and Digest Access Authentication, RFC 2617.

The Common Gateway Interface Version 1.1, RFC 3875.

The FastCGI specification.

## AUTHOR
Jan Kneschke <jan@kneschke.de>


lighttpd-angel

title: lighttpd-angel(8)

summary: monitor/supervise lighttpd daemon

text:
# lighttpd-angel(8)

## NAME
lighttpd-angel - monitor/supervise lighttpd daemon

## SYNOPSIS
lighttpd-angel <args>

## DESCRIPTION
lighttpd-angel monitors/supervises lighttpd daemon (started with <args>). lighttpd-angel will restart lighttpd if lighttpd exits for any reason, other than by signals sent by lighttpd-angel.

Send lighttpd-angel SIGTERM to initiate immediate shutdown of lighttpd.

Send lighttpd-angel SIGINT to initiate graceful shutdown of lighttpd.

Send lighttpd-angel SIGHUP to initiate graceful restart of lighttpd.

Send lighttpd-angel SIGUSR1 to initiate graceful reload of lighttpd config.

## SEE ALSO
Online Documentation:

https://wiki.lighttpd.net/InstallFromSource https://blog.lighttpd.net/articles/2007/09/02/there-is-an-angel-for-lighty/

## AUTHOR
Jan Kneschke <jan@kneschke.de>


atmaddr

package: linux-atm

title: atmaddr(8)

summary: list and maintain local ATM addresses

text:
# atmaddr(8)

## NAME
atmaddr - list and maintain local ATM addresses

## SYNOPSIS
atmaddr [-n] [itf]

atmaddr -r [itf]

atmaddr -a [itf] atm_addr

atmaddr -d [itf] atm_addr

atmaddr -V

## DESCRIPTION
atmaddr is used to list the local addresses configured for ATM interfaces and to manually change the list of addresses. If the interface number itf is omitted, interface 0 is used by default. The ATM address atm_addr can be any valid ATM SVC address, e.g. an E.164 address or an ATM Forum NSAP address.

If invoked without options, atmaddr lists the addresses that are currently configured on the specified interface.

Note that local ATM addresses are normally automatically maintained by the ILMI demon.

## OPTIONS
-a

append the specified address at the end of the list.

-d

delete the specified address from the list.

-n

numeric address output only. No address to name translation is attempted.

-r

reset (clear) the local address list of the specified interface.

-V

print the version number of atmaddr on standard output and exit.

## AUTHOR
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>

## SEE ALSO
ilmid(8)


atmarp

title: atmarp(8)

text:
# atmarp(8)

## NAME
atmarp - administer classical IP over ATM connections

## SYNOPSIS
atmarp -a

atmarp -c [[atm]number]

atmarp -q ip_addr [qos qos] [sndbuf bytes]

atmarp -s ip_addr [itf.]vpi.vci [qos qos] [sndbuf bytes] [temp] [pub] [null]

atmarp -s ip_addr atm_addr [qos qos] [sndbuf bytes] [temp] [pub] [arpsrv]

atmarp -d ip_addr [arpsrv]

atmarp -V

## DESCRIPTION
atmarp is used to maintain the ATMARP table of the ATMARP demon. The table can be listed, new PVC and SVC entries can be added, and existing entries can be deleted. In addition to that, atmarp is also used to create new IP over ATM interfaces.

Note that the kernel has its own ATMARP table containing only entries for destinations to which a connection exists. The table of atmarpd can also contain currently unused entries.

## OPTIONS
-a

list the current ATMARP table.

-c

create the specified IP interface. If the interface number is omitted, the operating system assigns the next free number and atmarp prints the resulting interface name (e.g. `atm0') on standard output.

-q

sets the QOS and the send buffer size to use as the default for all VCs generated for that IP network (ip_addr must be the address of the network).

-s

set up a PVC or create an SVC entry. The following options are recognized:

qos qos

uses the specified quality of service (see qos(7) for the syntax). UBR at link speed is used by default.

sndbuf bytes

tries to set the send buffer to the specified number of bytes. A system default value is used if sndbuf is not specified.

temp

does not mark the entry as permanent, i.e. it will time out and then be removed.

pub

publishes the entry (only relevant for ATMARP server). ATMARP requests for entries not marked for publishing yield an ATMARP_NAK response.

null

uses NULL encapsulation instead of LLC/SNAP encapsulation on the PVC. This option is not available for SVCs, because the LLC/SNAP header is required to identify ATMARP packets. null also implies that the entry is permanent.

arpsrv

identifies the entry pointing to the ATMARP server. Note that the node acting as the ATMARP server must have no ATMARP server entry in its ATMARP table.

-d

delete the specified ARP entry. In order to prevent accidental deletion of the ATMARP server entry, the arpsrv flag must be specified when deleting it.

-V

print the version number of atmarp on standard output and exit.

## FILES
/var/run/atmarpd.table

ATMARP table

## AUTHOR
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>

## SEE ALSO
atmarpd(8), clip(8), qos(7)


atmarpd

title: atmarpd(8)

summary: ATMARP demon

text:
# atmarpd(8)

## NAME
atmarpd - ATMARP demon

## SYNOPSIS
atmarpd [-b] [-d] [-D directory] [-l logfile] [-m] [-n]

atmarpd -V

## DESCRIPTION
atmarpd implements the ATMARP protocol as specified in RFC1577 and RFC1755. Address resolution requests are sent from the kernel (using a comparably simple protocol) to the ATMARP demon, which then performs the dialog with the network.

atmarpd can operate as an ATMARP client and as an ATMARP server. If also supports the concurrent use of several IP over ATM interfaces.

atmarpd is configured from the command line using the atmarp program. Unless debugging is enabled, the ATMARP table is written after every change to the file /var/run/atmarpd.table (or to a file with the same name in a different directory, if the -D option is used).

Note that atmarpd disables support for SVCs if signaling is not available at start time, i.e. if atmsigd is not running.

## OPTIONS
-b

Run in background (i.e. in a forked child process) after initializing.

-d

Enables (lots of) debugging output. By default, atmarpd is comparably quiet.

-D dump_dir

Changes the directory where atmarpd writes its table (atmarpd.table). By default, /var/run is used.

-l logfile

Write diagnostic messages to the specified file instead of to standard error. The special name syslog is used to send diagnostics to the system logger.

-m

Enables merging of incoming calls if the address is known. An incoming connection on which no InARP reply has been received yet, but which originates from an ATM address for which an ATMARP entry already exists, is automatically added to that entry. This assumes that there is a 1:1 mapping between IP addresses and ATMARP addresses. By default, this assumption is not made, which frequently results in the setup of duplicate connections. Note that RFC1577 requires that an ATMARP server sends an InARP request on an incoming connection. Merging may therefore violate RFC1577 in this case.

-n

Prints addresses in numeric format only, i.e. no address to name translation is attempted.

-V

Prints the version number of atmarpd on standard output and exits.

## FILES
/var/run/atmarpd.table

ATMARP table

/proc/atm/arp

table of currently active IP over ATM VCs

## BUGS
atmarpd removes ATMARP entries from the kernel table while refreshing them.

## AUTHOR
Werner Almesberger, EPFL ICA <werner.almesberger@epfl.ch>

## SEE ALSO
atmarp(8), atmsigd(8)


atmdiag

title: atmdiag(8)

summary: show ATM device driver diagnostics

text:
# atmdiag(8)

## NAME
atmdiag - show ATM device driver diagnostics

## SYNOPSIS
atmdiag [-z] [interface...]

## DESCRIPTION
atmdiag shows statistic counters maintained by ATM device drivers. If one or more interface numbers are specified, the statistics of only these interfaces are shown. Otherwise, statistics of all interfaces are displayed.

The following counters are shown for each AAL:

TX_okay

number of successfully sent PDUs.

TX_err

number of PDUs not sent because of errors.

RX_okay

number of successfully received PDUs.

RX_err

number of PDUs discarded because of errors.

RX_drop

number of PDUs dropped because of lack of memory.

## OPTIONS
-z

zero all counters after showing them.

## AUTHOR
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>

## SEE ALSO
atmdump(8), sonetdiag(8)


atmdump

title: atmdump(8)

summary: capture or generate ATM cells

text:
# atmdump(8)

## NAME
atmdump - capture or generate ATM cells

## SYNOPSIS
atmdump [-i] [ -t type [-g gfc] [-c] ] [itf.]vpi.vci

## DESCRIPTION
atmdump captures or generates single ATM cells ("AAL0"). When capturing cells, a time stamp, the cell header contents, and a hex dump of the cell payload are shown. When sending cells, the payload type, the generic flow control (GFC), and the cell loss priority (CLP) can be set.

In both modes of operation, the interface number, the VPI, and the VCI have to be specified.

When sending, atmdump expects the cell payload on standard input. If only less than 48 bytes can be read, the remaining space is padded with zero bytes.

## OPTIONS
-i

displays timestamps as the interval since the last cell reception. By default, the absolute time is displayed. This options is ignored in transmit mode.

-t type

selects transmit mode and specifies the payload type. A list of valid payload type numbers can be obtained by invoking atmdump without any arguments.

-g gfc

specifies the value of the GFC field. gfc has to be in the range from 0 to 15, default is zero.

-c

sets the cell loss priority flag, indicating low priority. By default, CLP is not set.

## RESTRICTIONS
Some device drivers may not pass OAM cells transparently.

## AUTHOR
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>

## SEE ALSO
atmdiag(8), clip(8), sonetdiag(8)


atmloop

title: atmloop(8)

summary: get/set loopback mode of ATM interfaces

text:
# atmloop(8)

## NAME
atmloop - get/set loopback mode of ATM interfaces

## SYNOPSIS
atmloop -s [-l level] [-r level] [itf]

atmloop [itf]

atmloop -q [itf]

atmloop -V

## DESCRIPTION
atmloop sets or shows the current loopback settings of an ATM interface, and allows to query the loopback modes supported by the interface.

Some ATM cards can be configured to echo data back to the driver (local loopback) or to the network (remote loopback). The echoing may be done at several different levels:

aal

AAL PDUs

atm

ATM cells

digital

bits sent to or received from the line interface

analog

the analog signal

The levels supported by an interface can be queried with the -q option. If invoked without options, atmloop displays the current loopback settings.

## OPTIONS
-s

set loopback mode. Followed by either -l or -r, both options to set local and remote loopback at the same time (if supported by the driver), or none of them to turn off any loopback.

-l level

enable local loopback.

-r level

enable remote loopback.

-q level

query loopback levels supported by the interface.

-V

print version number of atmloop on standard output and exit.

## AUTHOR
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>

## SEE ALSO
atmdiag(8), sonetdiag(8)


atmsigd

title: atmsigd(8)

summary: ATM signaling demon

text:
# atmsigd(8)

## NAME
atmsigd - ATM signaling demon

## SYNOPSIS
atmsigd [-b] [-c config_file] [-d] [-D dump_dir] [-l logfile] [-m mode] [-n] [-q qos] [-t trace_length] [-u uni_version] [[itf.]vpi.vci [input output]]

atmsigd -V

## DESCRIPTION
atmsigd implements the ATM UNI signaling protocol. Requests to establish, accept, or close ATM SVCs are sent from the kernel (using a comparably simple protocol) to the signaling demon, which then performs the dialog with the network.

Note that atmsigd is not able to accept or establish connections until the local ATM address of the interface is configured by ilmid or manually using atmaddr.

The default signaling VC (interface 0, VPI 0, VCI 5) can be overridden on the command line by specifying a different PVC address.

When overriding the default VC, optionally a pair of named pipes to use for communicating with the user of signaling can be specified. Normally, the kernel is the user of signaling and atmsigd opens a special socket for communication with it.

If atmsigd is killed, all system calls requiring interaction with it will return with an error and set errno to EUNATCH.

## OPTIONS
-b

Run in background (i.e. in a forked child process) after initializing.

-c config_file

Use the specified configuration file instead of /etc/atmsigd.conf If an option is specified in the configuration file and on the command line, the command line has priority.

-d

Enables (lots of) debugging output. By default, atmsigd is comparably quiet.

-D dump_dir

Specifies the directory to which atmsigd will write status and trace dumps. If -D is not specified, dumps are written to /var/tmp.

-l logfile

Write diagnostic messages to the specified file. The special name syslog is used to send diagnostics to the system logger, stderr is used to send diagnostics to standard error. If -l is absent, the setting in atmsigd.conf is used. If atmsigd doesn't specify a destination either, messages are written to standard error.

-m mode

Set the mode of operation. The following modes are available: user for the user side (the default), network for the network side (useful if you have two PCs but no switch), and switch for operation with a signaling relay in a switch.

-n

Prints addresses in numeric format only, i.e. no address to name translation is attempted.

-q qos

Configures the signaling VC to use the specified quality of service (see qos(7) for the syntax). By default, UBR at link speed is used on the signaling VC.

-t trace_length

Sets the number of entries that should be kept in the trace buffer. -t 0 disables tracing. If -t is not specified, atmsigd uses a default of 20 trace entries.

-u uni_version

Sets the signaling mode. The following modes are supported: uni30 for UNI 3.0, uni31 for UNI 3.1, uni31+uni30 for UNI 3.1 with 3.0 compatibility, uni40 for UNI 4.0, and uni40+q.2963.1 for UNI 4.0 with Q.2963.1 peak cell rate renegotiation.

-V

Prints the version number of atmsigd on standard output and exits.

## FILES
/etc/atmsigd.conf

default configuration file

/var/tmp/atmsigd.pid.status.version

default location of status dumps

/var/tmp/atmsigd.pid.trace.version

default location of signaling trace dumps

## DEBUGGING
When receiving a SIGUSR1 signal, atmsigd dumps the list of all internal socket descriptors. With SIGUSR2, it dumps the contents of the trace buffer. If a dump directory was set, dumps are written to files called atmsigd.pid.status.number and atmsigd.pid.trace.number, respectively, with number starting at zero and being incremented for every dump. If no dump directory is set, dumps are written to standard error.

Dumps are also generated whenever atmsigd detects a fatal error and terminates. No attempt is made to catch signals like SIGSEGV.

## BUGS
The generation of traces is a comparably slow process which may already take several seconds for only 100 trace entries. To generate a trace dump, atmsigd therefore forks a child process that runs in parallel to the signaling demon.

## AUTHOR
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>

## SEE ALSO
atmaddr(8), atmsigd.conf(4), ilmid(8), qos(7)


atmtcp

title: atmtcp(8)

summary: set up ATM over TCP connections

text:
# atmtcp(8)

## NAME
atmtcp - set up ATM over TCP connections

## SYNOPSIS
atmtcp [-d] [-v] command ...

atmtcp -V

## DESCRIPTION
The main purpose of atmtcp is to establish TCP connections and to configure them as virtual ATM devices. Such pairs of "ATM over TCP" devices are connected as if they were real ATM adapters linked by a cable or fiber, i.e. SDUs sent on a given VPI/VCI are received at the other end on the same VPI/VCI.

Virtual interfaces and ATM over TCP connections are called links. Other link types supported by atmtcp are real interfaces, files for recording and playback of ATM traffic, and printing a hex dump of the PDU content on standard output. Any pair of such links can be connected with atmtcp. If additional links are attached to such a connection, they send to all other links, except to the first link and the respective sender, and they receive from all other links.

atmtcp can operate with two types of virtual interfaces: ephemeral or persistent. By default, atmtcp interfaces are ephemeral. When the atmtcp process that created an interface terminates, the virtual ATM device is removed as soon all VCs are closed. However, if the interface was previously created as a persistent interface, only the communication stops, but the interface and all VCs on it remain intact. Attempts to send data on an atmtcp interface in this state fail silently, i.e. the interface behaves just like a real ATM interface without a wire. A new atmtcp process can then attach to the interface and resume operation. Persistent interfaces need to be removed explicitly.

If atmtcp has any readable links after processing the command line, it enters a loop to perform the data forwarding. If no readable links have been specified, atmtcp terminates after processing the command line. If any setup operation fails, atmtcp terminates at this point and does not attempt to cancel previous operations (e.g. creation of permanent interfaces).

## OPTIONS
-d

print detailed progress information on standard error.

-v

print some progress information on standard error.

-V

print version number of atmtcp on standard output and exit.

## COMMANDS
create [itf]

create a persistent interface. If no interface number is specified, atmtcp uses the default value 0.

remove [itf]

remove a persistent interface. If the interface is still in use, it is marked as ephemeral and will be removed as soon as all VCs are closed. If no interface number is specified, atmtcp uses the default value 0.

virtual [itf]

link to the corresponding virtual (ATM over TCP) interface. If no interface number is specified, the kernel assigns the first available number.

real [itf]

link to the corresponding ATM interface. If no interface number is specified, atmtcp uses the default value 0. If a link requests that a VC be opened, atmtcp will attempt to open a VC with the specified QoS parameters on that interface. If the operation succeeds, data can be sent or received on that VC. If the operation fails, an error code is returned to the requester. Note that only data arriving on open VCs can be received and that a real ATM interface never initiates a connection. atmtcp can share ATM interfaces with other applications.

connect host [port]

connect to an instance of atmtcp running on the specified host. If the port argument is omitted, atmtcp uses the default port 2812.

switch host line [port]

like connect, but connects to an ATM over TCP "switch" and selects the specified virtual line.

listen [port]

listen for an incoming ATM over TCP connection. If the port argument is omitted, atmtcp uses the default port 2812. atmtcp waits until the connection is established. Only one connection is accepted per listen command.

listen-bg [port]

like listen, but run in background after beginning to listen.

read file [stream]

play back all streams from the specified file. If a stream number is specified, only that stream is played back.

write file

record the traffic of all links in the specified file. The PDUs from each link are stored in a stream with the same number as the link.

print

print a hex dump of the content of all received PDUs on standard output.

bg

continue to run in background (i.e. in a forked child process).

wait [seconds]

wait for the specified number of seconds. If no time is specified, atmtcp waits for a newline on standard input.

## RESTRICTIONS
Due to recent protocol changes, atmtcp is currently not compatible with the ATM over TCP "switch".

Only AAL SDUs are exchanged, no segmentation or reassembly is performed. That implies that using different AALs (e.g. AAL5 and AAL0) on either side will reveal limitations of this emulation.

The atmtcp process needs to run during the the whole lifetime of the connection.

## EXAMPLES
Create a pair of virtual ATM over TCP interfaces on the local host and connect them:

```
  # session A

  atmtcp virtual listen

  # session B

  atmtcp virtual connect localhost
```

Create virtual interface 1, connect it to real ATM interface 0, then start atmsigd on the virtual interface, and log all the traffic in a file:

```
  atmtcp virtual 1 real 0 write /tmp/log

  atmsigd 1.0.5
```

Take the previously created file and examine the traffic sent from atmsigd using saaldump:

```
  # session A

  atmtcp virtual 1 read /tmp/log 0 wait

  # session B

  saaldump 1.0.5

  # press [Enter] in session A
```

## AUTHOR
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>

## SEE ALSO
atmdiag(8)