Hi Mark,
> It is marked as fixed in net-snmp/5.4.1~dfsg-1, however it is also marked as
> found in net-snmp/5.4.1~dfsg-4 so it still appears in the lenny RC bug list.
>
> From my reading of the bug report, this issue is still effecting lenny, and
> Josselin has proposed a fix.
debian/patches/4
On Tuesday 11 November 2008 03:33:08 Josselin Mouette wrote:
> Regardless of the behavior of the daemon (which should indeed close
> stdout), you must call db_stop before doing anything else.
>
> This bug is still present in the stable release and breaks security
> updates.
Jochen, Thomas & Noah,
Le lundi 10 novembre 2008 à 16:59 +0100, Jochen Friedrich a écrit :
> Hi Josselin,
>
> > It has nothing to do with the daemon, but rather, as Ferenc Wagner
> > diagnosed, with the postinst script not calling db_stop as expected.
>
> Nope, it was a bug with the daemon (snmpd and snmptrapd behaved
Hi Josselin,
> It has nothing to do with the daemon, but rather, as Ferenc Wagner
> diagnosed, with the postinst script not calling db_stop as expected.
Nope, it was a bug with the daemon (snmpd and snmptrapd behaved
differently here) and has been fixed by upstream in 5.4.2. In Debian,
the bug is
found 453123 5.2.3-7etch4
severity 453123 serious
tag 453123 + patch
thanks
I’ve just been bitten by this problem while upgrading a stable system.
It has nothing to do with the daemon, but rather, as Ferenc Wagner
diagnosed, with the postinst script not calling db_stop as expected.
Cheers,
--
5 matches
Mail list logo
