> when i use the alarm
> mechanism it is trying to see whether any alarm is to be run and checks
> outstanding agent requests every second by means of timeout in select()
> which is present in receive() of snmpd.c. does this mean that alarm is the
> only way of doing delayed processing?
> in the main loop of receive() in snmpd.c instead of select() getting
> timeout every second only when alarms are registered why can't it timeout
> always every second to see whether any outstanding requests have been
> processed? if one second is too less timeout can be higher but checking
> for outstanding requests periodically will be really useful. kindly
> clarify this to me.
>
i am sorry for providing wrong information. the select actually times out
every half a second. the timeout value given is 500000 microseconds. but
still it will be better if the blocking is not allowed to happen even
if no requests or alarms are present.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
|
