Hi,
<<We"ve had
some people with memory problems with snmptrapd, which seem to be
(at least partially) because of the new sub-agent code that implements the
notificaiton log mib. Unfortunately, there is no way to configure snmptrapd to
not be a sub-agent. I think this is a bug.>>
(at least partially) because of the new sub-agent code that implements the
notificaiton log mib. Unfortunately, there is no way to configure snmptrapd to
not be a sub-agent. I think this is a bug.>>
I think it is a bug,
I do not know any of this notification log mib, but even we do not have
the flag as some of you suggested, the memory should still not grow
unlimited.., and this happened in earliest version (5.1.1) too, at that time, I
am not sure does this new sub-agent code exist ?
Your support are
highly appreciated.
Lan
