diff options
| author | zi <zi@FreeBSD.org> | 2012-04-04 20:13:44 +0800 |
|---|---|---|
| committer | zi <zi@FreeBSD.org> | 2012-04-04 20:13:44 +0800 |
| commit | bdc25f7df0abd8492558db378a5f83fceacc4e11 (patch) | |
| tree | 66368a343aa5a4bab88e312c2e8d900a3c9817af /UPDATING | |
| parent | 9973ef94a11d7eb876c67e32bea1915e1461220d (diff) | |
| download | freebsd-ports-gnome-bdc25f7df0abd8492558db378a5f83fceacc4e11.tar.gz freebsd-ports-gnome-bdc25f7df0abd8492558db378a5f83fceacc4e11.tar.zst freebsd-ports-gnome-bdc25f7df0abd8492558db378a5f83fceacc4e11.zip | |
- Add note about net-mgmt/net-snmp rc script pid_file change
Feature safe: yes
Diffstat (limited to 'UPDATING')
| -rw-r--r-- | UPDATING | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -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 |