aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorMark Felder <feld@FreeBSD.org>2015-10-19 15:14:42 +0000
committerMark Felder <feld@FreeBSD.org>2015-10-19 15:14:42 +0000
commitf55c442ccfe88fd0f27ae29c18b6be69aaaba49a (patch)
tree9e70167e99a2214a51a679c43391688c24732762 /UPDATING
parent529fb56e36cbfde70ed762f4425eeb9c16ba7fb4 (diff)
downloadports-f55c442ccfe88fd0f27ae29c18b6be69aaaba49a.tar.gz
ports-f55c442ccfe88fd0f27ae29c18b6be69aaaba49a.zip
Document file ownership changes for www/varnish4 update
Notes
Notes: svn path=/head/; revision=399690
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING20
1 files changed, 20 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 9fd175956f77..c865b7bb2b7f 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,26 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20151019:
+ AFFECTS: users of www/varnish4
+ AUTHOR: feld@FreeBSD.org
+
+ Varnish has been updated to 4.1.0. As part of the update an effort has
+ been made to increase the security of the varnish daemons by utilizing
+ separate UIDs. Users who upgrade will likely run into a permissions
+ issue as a result. The simplest solution is to delete files varnish
+ will recreate with the correct permissions and to adjust permissions
+ of existing log files.
+
+ The following changes will allow you to start varnishd, varnishlog,
+ and varnishncsa successfully:
+
+ # rm -r /usr/local/varnish/$(hostname)
+ # rm /var/run/varnishlog.pid
+ # rm /var/run/varnishncsa.pid
+ # chown varnishlog /var/log/varnish.log
+ # chown varnishlog /var/log/varnishncsa.log
+
20151015:
AFFECTS: users of devel/subversion, its bindings and www/mod_dav_svn
AUTHOR: lev@FreeBSD.org