Re: Segfault on 5.4.2.1 (Redhat) when using DISMAN-SCHEDULE-MIB cron or repeat directives with numeric OIDs

2009-09-19 Thread Max
Follow up .. GDB output: 0 0x006fe285 in memmove () from /lib/libc.so.6 #1 0x00cc1b22 in snmp_set_var_value (vars=0x95d19d0, value=0x1 , len=10) at snmp_client.c:895 #2 0x00cf1caa in snmp_varlist_add_variable (varlist=0x9583300, name=0x0, name_length=0, type=4 '\004', value=0x1 , len=10

Re: Lm-Sensors3 support

2009-09-19 Thread Billy DeVincentis
Thomas Anders wrote: Billy DeVincentis wrote: I am just trying to find out if there is support for building against the newer lmsensors in any version of this program. Try 5.5.rc3 (or later) which should have some support for the v3 lmsensors API. +Thomas

Segfault on 5.4.2.1 (Redhat) when using DISMAN-SCHEDULE-MIB cron or repeat directives with numeric OIDs

2009-09-19 Thread Max
Hi, Trying to schedule the agent to call an SNMP set on a module that is implemented through the agent using the pass_persist framework: * We can call the SET from the command line using snmpset without issue * Using symbolic OIDs for built-in MIBs does *NOT* trigger the segfault (for example, the