diff --git a/man/daemon.xml b/man/daemon.xml index 072529eeec..b5ae08473d 100644 --- a/man/daemon.xml +++ b/man/daemon.xml @@ -448,37 +448,27 @@ Other Forms of Activation - Other forms of activation have been suggested and - implemented in some systems. However, there are often simpler or - better alternatives, or they can be put together of combinations - of the schemes above. Example: Sometimes, it appears useful to - start daemons or .socket units when a - specific IP address is configured on a network interface, - because network sockets shall be bound to the address. However, - an alternative to implement this is by utilizing the Linux - IP_FREEBIND socket option, as accessible - via FreeBind=yes in systemd socket files (see - systemd.socket5 - for details). This option, when enabled, allows sockets to be - bound to a non-local, not configured IP address, and hence - allows bindings to a particular IP address before it actually - becomes available, making such an explicit dependency to the - configured address redundant. Another often suggested trigger - for service activation is low system load. However, here too, a - more convincing approach might be to make proper use of features - of the operating system, in particular, the CPU or I/O scheduler - of Linux. Instead of scheduling jobs from userspace based on - monitoring the OS scheduler, it is advisable to leave the - scheduling of processes to the OS scheduler itself. systemd - provides fine-grained access to the CPU and I/O schedulers. If a - process executed by the init system shall not negatively impact - the amount of CPU or I/O bandwidth available to other processes, - it should be configured with + Other forms of activation have been suggested and implemented in some systems. However, there are + often simpler or better alternatives, or they can be put together of combinations of the schemes + above. Example: Sometimes, it appears useful to start daemons or .socket units + when a specific IP address is configured on a network interface, because network sockets shall be bound + to the address. However, an alternative to implement this is by utilizing the Linux + IP_FREEBIND/IPV6_FREEBIND socket option, as accessible via + FreeBind=yes in systemd socket files (see + systemd.socket5 for + details). This option, when enabled, allows sockets to be bound to a non-local, not configured IP + address, and hence allows bindings to a particular IP address before it actually becomes available, + making such an explicit dependency to the configured address redundant. Another often suggested trigger + for service activation is low system load. However, here too, a more convincing approach might be to + make proper use of features of the operating system, in particular, the CPU or I/O scheduler of + Linux. Instead of scheduling jobs from userspace based on monitoring the OS scheduler, it is advisable + to leave the scheduling of processes to the OS scheduler itself. systemd provides fine-grained access + to the CPU and I/O schedulers. If a process executed by the init system shall not negatively impact the + amount of CPU or I/O bandwidth available to other processes, it should be configured with CPUSchedulingPolicy=idle and/or - IOSchedulingClass=idle. Optionally, this may - be combined with timer-based activation to schedule background - jobs during runtime and with minimal impact on the system, and - remove it from the boot phase itself. + IOSchedulingClass=idle. Optionally, this may be combined with timer-based activation + to schedule background jobs during runtime and with minimal impact on the system, and remove it from + the boot phase itself. diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml index 253da8a6d4..3aff453185 100644 --- a/man/systemd.socket.xml +++ b/man/systemd.socket.xml @@ -568,26 +568,23 @@ IPTOS= - Takes an integer argument controlling the IP - Type-Of-Service field for packets generated from this socket. - This controls the IP_TOS socket option (see - ip7 - for details.). Either a numeric string or one of - , , - or may - be specified. + Takes an integer argument controlling the IP Type-Of-Service field for packets + generated from this socket. This controls the IP_TOS socket option (see + ip7 for + details.). Either a numeric string or one of , , + or may be specified. IPTTL= - Takes an integer argument controlling the IPv4 - Time-To-Live/IPv6 Hop-Count field for packets generated from - this socket. This sets the IP_TTL/IPV6_UNICAST_HOPS socket - options (see - ip7 - and - ipv67 - for details.) + Takes an integer argument controlling the IPv4 Time-To-Live/IPv6 Hop-Count field for + packets generated from this socket. This sets the + IP_TTL/IPV6_UNICAST_HOPS socket options (see ip7 and + ipv67 for + details.) @@ -662,20 +659,18 @@ FreeBind= - Takes a boolean value. Controls whether the - socket can be bound to non-local IP addresses. This is useful - to configure sockets listening on specific IP addresses before - those IP addresses are successfully configured on a network - interface. This sets the IP_FREEBIND socket option. For - robustness reasons it is recommended to use this option - whenever you bind a socket to a specific IP address. Defaults - to . + Takes a boolean value. Controls whether the socket can be bound to non-local IP + addresses. This is useful to configure sockets listening on specific IP addresses before those IP + addresses are successfully configured on a network interface. This sets the + IP_FREEBIND/IPV6_FREEBIND socket option. For robustness + reasons it is recommended to use this option whenever you bind a socket to a specific IP + address. Defaults to . Transparent= Takes a boolean value. Controls the - IP_TRANSPARENT socket option. Defaults to + IP_TRANSPARENT/IPV6_TRANSPARENT socket option. Defaults to .