svn commit: r472097 - in head/databases/mongodb36: . files

[Eugene Grosbein]

10.06.2018 4:33, Steve Wills wrote:

> Author: swills
> Date: Sat Jun  9 21:33:55 2018
> New Revision: 472097
> URL: https://svnweb.freebsd.org/changeset/ports/472097
> 
> Log:
>   databases/mongodb36: upgrade to 3.6.5
>   
>   PR:		228806
>   Submitted by:	dev at dudu.ro (maintainer)

[skip[

> Modified: head/databases/mongodb36/files/mongod.in
> ==============================================================================
> --- head/databases/mongodb36/files/mongod.in	Sat Jun  9 21:30:38 2018	(r472096)
> +++ head/databases/mongodb36/files/mongod.in	Sat Jun  9 21:33:55 2018	(r472097)
> @@ -30,7 +30,7 @@ load_rc_config $name
>  : ${mongod_enable="NO"}
>  %%LEGACY_LIMITS%%: ${mongod_limits="NO"}
>  : ${mongod_dbpath="/var/db/mongodb"}
> -: ${mongod_flags="--logpath ${mongod_dbpath}/mongod.log --logappend"}
> +: ${mongod_flags="--logpath ${mongod_dbpath}/mongod.log --logappend --setParameter=disabledSecureAllocatorDomains=\*"}
>  : ${mongod_user="mongodb"}
>  : ${mongod_group="mongodb"}
>  : ${mongod_config="%%PREFIX%%/etc/mongodb.conf"}

The change seems suspictious to uneducated eye. Perhaps, some commentary in the commit log
would be useful, like: mongodb36 now requires disabling "SecureAllocator" that uses mlock()
to be useful for restricted users, or else it crashes with SIGABRT in fassert()
complaining "Failed to mlock: Operation not permitted".