Date: Mon, 02 Apr 2018 21:10:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 226907] databases/mongodb36: failed to start mongod due to "limits: NO: No such file or directory" Message-ID: <bug-226907-13-EzoKhKSD5x@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-226907-13@https.bugs.freebsd.org/bugzilla/> References: <bug-226907-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226907 Mateusz Piotrowski <0mp@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |0mp@FreeBSD.org Attachment #192119| |maintainer-approval?(0mp@Fr Flags| |eeBSD.org) --- Comment #8 from Mateusz Piotrowski <0mp@FreeBSD.org> --- Created attachment 192119 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D192119&action= =3Dedit Patch adding support for the new ${name}_limits mechanics (databases/mongod= b36) Here's a patch, which should fix the issue for the systems with the new behavior. It also should preserve the old behavior for the old systems (10.= 4, 10-STABLE, 11.1). I've built this port on my dev machine running 12.0-CURRENT r331748 and it seems to build just fine. The service script looks fine as well. Could you please review this patch and test it on the systems with the lega= cy behavior (10.4, 10-STABLE, 11.1)? Thanks! --=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-226907-13-EzoKhKSD5x>