Committing ${name}_limits patches for the rc files of various databases

[Kirill Ponomarev]

On 04/21, Mateusz Piotrowski wrote:
> Hello,
> 
> A few weeks ago I discovered a regression caused by the standardization
> of the mechanism used to limit daemons resources with limits(1). This
> feature was introduced in r328331[1]. Basically, it defines that
> limits(1) could be controlled via rc.conf(5) using ${name}_limits
> variables as defined in rc.subr(5).
> 
> Unfortunately, many database rc scripts have already used ${name}_limits
> variables with incompatible semantics. This is why I worked with some
> FreeBSD committers and developers on a set of patch for those affected
> databases. Thanks to their reviews and testing effort I was able to
> open an issue on Bugzilla for every affected database port and provide a
> few revisions of patchs for each of them.
> 
> Some of the patches were already incorporated into the ports tree, but
> many of them are still waiting to be committed. Recently, an update to
> database/mongodb36 was committed[2], which not only does not solve the
> problem of the mongodb36 daemon to be broken on FreeBSD 12.0-CURRENT but
> also introduces parts of my old patches, which were marked obsolete[3].

Please contact maintainer and resolve these issues. I didn't see any
objections and proposals from you in this PR.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 545 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20180421/ed917455/attachment.sig>