aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorRyan Steinmetz <zi@FreeBSD.org>2012-04-04 12:13:44 +0000
committerRyan Steinmetz <zi@FreeBSD.org>2012-04-04 12:13:44 +0000
commit011ae6547c22bad4573a58e5d2b0724a26247957 (patch)
treee980a6f5fa5489703c9de52288d2bb2b8db76856 /UPDATING
parent0d6748b911cb8719e1b9a37df70b14fde5c7ca24 (diff)
downloadports-011ae6547c22bad4573a58e5d2b0724a26247957.tar.gz
ports-011ae6547c22bad4573a58e5d2b0724a26247957.zip
- Add note about net-mgmt/net-snmp rc script pid_file change
Feature safe: yes
Notes
Notes: svn path=/head/; revision=294197
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING12
1 files changed, 12 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 3dab24b7d433..d84ba967c980 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,18 @@ 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.
+20120404:
+ AFFECTS: users of net-mgmt/net-snmp
+ AUTHOR: zi@FreeBSD.org
+
+ The net-snmp startup script now specifies a new pid_file to avoid a
+ conflict that existed with bsnmpd. As a result, the startup script
+ cannot find currently running versions of snmpd.
+
+ You will need to either stop the daemon before upgrading or locate the
+ PID of snmpd and manually kill it after upgrade. Then, start the daemon
+ as you normally would.
+
20120326:
AFFECTS: users of www/tomcat7
AUTHOR: ale@FreeBSD.org