Short feedback on the fix. I have 2 KVM based 14.04 64bit systems
which were not affected by this bug UNTIL the 3.13.0-46.77 fix was
release. On 1 of the 2 systems everything seems fine on the other IPv6
is not available directly after booting thus e.g. nginx can not bind to
the configured IPv6
Since todays kernel update (3.13.0-46.76 - 3.13.0-46.77) I also see
this message in my kern.log It has not been there before and I'm just
wondering what will happen if this continues as the too long value
seems to be continiously rising and the sample rate is being lowered
Mar 3 07:14:57 sigma
Public bug reported:
Between the precise and the trusty versions of this package the path to
the daemon has changed. In precise it installs to
/usr/sbin/rtpproxy
but in trusty it installs to
/usr/bin/rtpproxy
Since the /etc/init.d/rtpproxy script has not been changed, rtpproxy
wont start at
