Hi
On Mon, 29 May 2023 07:49:43 -0400 Alex wrote:
> I have a fedora37 system using bind-chroot-9.18.15 and shortly after reboot
> I received the following message:
> [ 54.354236] mmap: named (1471): VmData 3287973888 exceed data ulimit
> 3145728000. Update limits.
The named-chroot.service does:
ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} -t /var/named/chroot $OPTIONS
Try perhaps to make an override of named-chroot.service as:
[Service]
LimitDATA=infinity:infinity
Refs: man systemd.exec systemd.resource-control systemd.directives
This is weird: AFAIK, in a service, except if using pam (with PAMName=) and
thus pam_limits indirectly, there should be no ulimit for data.
This is perhaps named itself that set this limit, or DefaultLimitDATA= is set
in /etc/systemd/system.conf (or in the system.conf.d directories).
> Previously I would adjust /etc/security/limits.conf, but it seems now I
> must use cgroups to do this? I've located the following information, but I
> don't understand how to adjust these values.
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/ch01
This is rather old.
Nowadays, systemd manages the cgroups itself and provides parameters for
controlling them. See man systemd.resource-control
--
francis
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
