Date: Fri, 18 Feb 2022 11:05:30 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 262031] net/ntp 4.2.8p15_4 starts with error: Cannot set RLIMIT_MEMLOCK Message-ID: <bug-262031-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262031 Bug ID: 262031 Summary: net/ntp 4.2.8p15_4 starts with error: Cannot set RLIMIT_MEMLOCK Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: cy@FreeBSD.org Reporter: p5B2E9A8F@t-online.de Flags: maintainer-feedback?(cy@FreeBSD.org) Assignee: cy@FreeBSD.org Having read https://reviews.freebsd.org/D21581 Administrators wishing to preserve the historic behavior can do so by adding 'rlimit memlock 32' to ntp.conf.=20 Having done so starting ntpd still issues errors in logfiles ntpd[96018]: Cannot set RLIMIT_MEMLOCK: Operation not permitted As adding rlimit memlock to ntp.conf makes no difference the problem is not solved. Setting rlimit is not recognized by ntpd. ntp-4.2.8p15_4: FreeBSD_version: 1300139 build_timestamp: 2022-02-15T03:34:40+0000 built_by : poudriere-git-3.3.99.20211130 cpe : cpe:2.3:a:ntp:ntp:4.2.8p15:::::freebsd13:x86:4 port_checkout_unclean: no port_git_hash : a18d5b7f5 ports_top_checkout_unclean: no ports_top_git_hash: 0ecdbd461 repo_type : binary repository : local --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262031-7788>