Re: Config file never re-read after SIGHUP

[Wes H. <har...@us...>]

>>>>> On Wed, 4 Dec 2002 15:11:07 -0800 (PST), Bob Blair <bbl...@ya...> said:

Bob> In debugging it I found that after failing on each GETNEXT to the
Bob> proxied agent, the proxying agent ends up sitting on the select
Bob> in snmp_synch_response_cb() instead of the select in the agent's
Bob> main loop.  This works out for most things -- subsequent requests
Bob> are handled correctly -- but the agent never gets back to the
Bob> agent main loop in order to check the reconfig flag and reread
Bob> the configuration.

The proxy code in the 4.x series is horrible, so...

Bob> I figure someone must have noticed this before.  Is
Bob> there a work-around?  Is it fixed in 5.0?

Probably?  The proxy code was completely rewritten for the 5.0 line
and should be much much better.  Try it and see if it fixes your problem.

-- 
Wes Hardaker
Network Associates Laboratories