|
Lines 5-10
they are unavoidable.
Link Here
|
| 5 |
You should get into the habit of checking this file for changes each time |
5 |
You should get into the habit of checking this file for changes each time |
| 6 |
you update your ports collection, before attempting any port upgrades. |
6 |
you update your ports collection, before attempting any port upgrades. |
| 7 |
|
7 |
|
|
|
8 |
20180402: |
| 9 |
AFFECTS: users of databases/{arangodb32,arangodb33,clickhouse,mariadb100-server,mariadb101-server,mariadb102-server,mariadb55-server,mongodb,mongodb32,mongodb34,mongodb34-rocks,mongodb36,mysql55-server,mysql56-server,mysql57-server,mysql80-server,mysqlwsrep56-server,mysqlwsrep57-server,percona55-server,percona56-server,percona57-server} |
| 10 |
AUTHOR: 0mp@FreeBSD.org |
| 11 |
|
| 12 |
The mechanism to set process resource limits (${name}_limits) has changed. |
| 13 |
|
| 14 |
Many databases implement their own ways to limit resources from rc.conf(5). A |
| 15 |
popular implementation is defining ${name}_limits, which defaults to "NO". If |
| 16 |
set to "YES", however, limits(1) is run before starting the database service. |
| 17 |
|
| 18 |
The new mechanism runs limits(1) by default and uses the ${name}_limits |
| 19 |
variable to let the user pass extra flags to the limits(1) command. See |
| 20 |
rc.subr(8) for details. |
| 21 |
|
| 22 |
For example, the equivalence of the old "mongod_limits='YES'" configuration |
| 23 |
is now "mongod_limits='-U mongodb'". |
| 24 |
|
| 25 |
This change affects systems running 12-CURRENT. This feature has been |
| 26 |
backported to 11-STABLE and will be present in 11.2-RELEASE. |
| 27 |
|
| 8 |
20180401: |
28 |
20180401: |
| 9 |
AFFECTS: users of mail/dovecot and mail/dovecot-pigeonhole |
29 |
AFFECTS: users of mail/dovecot and mail/dovecot-pigeonhole |
| 10 |
AUTHOR: adamw@FreeBSD.org |
30 |
AUTHOR: adamw@FreeBSD.org |