I have an snmp subagent that normally runs without a problem. I changed the timeout parameter in the reg file and I now get an snmpdx core dump. Here's the old configuration that ran OK:

agents =
{
{
name = "mntagent"
subtrees = { mntagent }
timeout = 4000000
watch-dog-time = 2
port = 7041
}
}


Here's the new configuration that seems to cause snmpdx to core dump:

agents =
{
{
name = "mntagent"
subtrees = { mntagent }
timeout = 20000000
watch-dog-time = 2
port = 7041
}
}


Has anybody seen anything like this before?? I checked /var/adm/messages, but there's nothing in there that gives a clue about errors surrounding this problem. But....I do have the core file which shows a SEG VIOLATION in snmpdx.

Oh, BTW...my system info:
SunOS ecgdev 5.8 Generic_108528-18 sun4u sparc SUNW,Sun-Blade-100

Thanks in advance for any help!

Um, since you've changed only the timeout parameter, looks like this value is not accepted. i guess you can always revert back the changes, but what the actual core dump file says ?

The value is valid. A timeout value up to the max-agent-timeout value specified in snmpdx.rsrc is valid. I currently have the default value of 999999999 as the max-agent-timeout. My 20000000 should be acceptable.

Even if it was not valid (and I'm sure it is), I would not expect a core dump of snmpdx complaining about a SEG VIOLATION. I would expect some type of error instead.