![]() ![]() The SystemCallFilter= unit file setting gained support for pre-defined, named system call filter sets. (Effectively this is an increase of 512 → 4915 for service units, given the kernel's default pid_max setting.) The per-service task maximum has been changed to 15% using this functionality. The value is taken relative to the configured maximum number of processes on the system. In similar fashion TasksMax= takes percentage values now, too. Similarly, systemd-logind's RuntimeDirectorySize= option now also optionally takes percentage values. This allows scaling service resources neatly with the amount of RAM available on the system. The percentage is taken relative to the amount of physical memory in the system (or in case of containers, the assigned amount of memory). MemoryLimit= and related unit settings now optionally take percentage specifications. They also have ProtectHome=read-only and ProtectSystem=strict enabled, so they are not able to make any permanent modifications to the system. Services started in this way have PrivateTmp= and RemoveIPC= enabled, so that any resources allocated by the service will be cleaned up when the service exits. They can be resolved using the new nss-systemd.so NSS module. If DynamicUser=yes is specified, user and group IDs will be allocated from the range 61184.65519 for the lifetime of the service. Support for dynamically creating users for the lifetime of a service has been added. Ports to other architectures like ARM64 and POWER are in the works by the community. Leap works with X86_64 and deployment scenarios can be run for physical, virtual, host and guest, and cloud. ![]() ![]() Support for RFC6698/RFC7671 DANE TLSA peer authentication.Support for OCB mode added to libcrypto.40 and 56 bit cipher support removed from libssl.RC4 removed from DEFAULT ciphersuites in libssl.Leap 15 has received all necessary backports and uses the same Enterprise Linux Kernel that SUSE uses. System Administrators and small businesses can use Leap for hosting web and mail servers or for network management with DHCP, DNS, NTP, Samba, NFS, LDAP, and hundreds of other services. Sysadmins can take full advantage of the network management protocol Dynamic Host Configuration Protocol (DHCP), allocate resources of the Domain Name System (DNS) or offer client computers access files over a Network File System (NFS). A prominent feature list and intricate details can be found on. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |